Set up Tensorworks for your company

Everything in Tensorworks lives in an organization: its projects, resources, users and roles belong to the organization rather than to any one person. Everyone who signs up gets one of their own, and Enterprise turns one into your company's, with verified domains, directory sync and per-seat billing.

This guide walks an administrator through setting one up, from upgrading it to connecting a directory. For help with a larger rollout, use our contact form.

At a glance

Plan
Enterprise, $500.00 per month plus $30.00 per seat
People
Added by email, or synced over SCIM or HRIS
Domains
Verified with a DNS TXT record
Sign-in
Each person's own account, with optional two-factor authentication
Encryption
AES-256-GCM, keys of its own per account, organization, project and resource

Getting started

Before you begin

  • Who can do this: the organization's owner and its admins add domains, connect a directory and manage users; only its owner changes the plan and its billing.
  • What you'll need: access to your email domain's DNS settings to verify it, and, for directory sync, someone who administers your identity provider or HR system.
  • Plan: Enterprise is billed $500.00 per month plus $30.00 per seat per month, and everyone who has joined the organization's team is a seat, its owner too; an invitation costs nothing until it is accepted. Each seat holds 100 GB of files, shared between them. Paying yearly costs 10 months. Verified domains, single sign-on and directory sync are part of Enterprise.
  • Sign-in: everyone has their own Tensorworks account, protected by its password and, if they turn it on, two-factor authentication. People at a verified domain can also sign in through your identity provider (SAML or OIDC); see Single sign-on.

Step 1

Upgrade your organization

Use the organization you got when you signed up, or make a new one from All organizations, at the foot of the sidebar's organization menu, (you may own 1 organization on Free, and any number on Pro or Enterprise). You are its owner; nobody signs in to the organization itself.

  1. Pick the organization in the sidebar and open Settings › Organization to give it your company's name.
  2. Open Settings › Billing and choose Upgrade to Enterprise.
  3. Pay with a card, by the month or the year. The first invoice has the base fee and a seat for everyone who has joined. Or try Enterprise free for 14 days first, with no card: add one before it ends to keep it. To pay by invoice instead, ask us and we'll turn it on for your organization.

Enterprise belongs to the organization, not to whoever paid for it: it has its own card and invoices, and its owner manages its billing. Its users need no plan of their own.

Step 2

Verify your domains

Verifying an email domain proves your company holds it. People with an address there become the organization's own: once added, they join at once. Anyone else you add is invited instead, and may decline or leave.

  1. Open Manage org › User Sync. Under Domain emails, enter the domain (for example example.com) and choose Add domain.
  2. Add the TXT record shown. The token is random and belongs to your organization; keep any TXT records already there.
  3. Choose Verify. DNS changes can take a while to appear; if the domain stays Not verified, check that the record's name and value match exactly and try again.

You can verify several domains. Each belongs to one organization at a time.

  • Existing invitations: verifying a domain joins anyone already invited at that address straight away.
  • Keep the record: before anyone joins through a domain, Tensorworks checks the record again. If it's gone, the domain is no longer verified and people there are invited rather than joined, and another organization that publishes its own record may take the domain over.
DNS record
Name:  _tensorworks-verification.example.com
Type:  TXT
Value: tensorworks-verification=<token>

Step 3

Add your people

Choose how people arrive in Manage org › User Sync: invite by email, domain emails and directory sync. Turn on any or all; turning one off stops it adding anyone.

  • By hand (the default): open Chat and choose Invite, one email address per line. People at a verified domain join at once, joining when they register if they don't have an account yet; anyone else gets an invitation.
  • Directory sync: people join and leave as your identity provider or HR system says, over SCIM or HRIS. See Connect your directory.

Admins can remove someone from their page under Chat, which frees the seat. People your directory manages are removed through the directory instead.

Someone invited before they have an account signs up straight into your organization; they get no organization of their own until they make one.

Step 4

Decide what people open

Someone you invite opens only the roles you choose on their invitation, and someone your directory adds only the roles of their groups. You can change anyone's access later on their page.

AccessAllows
OwnerThe person who made the organization, or took it over. Runs it like an admin, alone manages its billing, and is always on its team.
AdminRuns the organization: its name, domains, directory, users and roles. Works only in the projects and resources they are granted, unless they also have full access, which an admin can give themselves.
Full accessWorks in everything, as the organization's owner would, including creating, renaming and archiving projects.
LimitedOpens only what their roles, their directory groups' roles and their own grants open.

A role grants whole projects (with their subprojects and anything added later) or single resources, each with full access, read only, or custom permissions such as which columns a card may move between or who may upload and delete files. Grants add up, and the server enforces every one of them.

A grant may also allow what opening something never does: Create resources in a project or at the root, Archive resources, Invite guests and Remove guests, for a whole project and everything in it or for one resource alone. A guest is someone given that one project or resource, whether already in your organization or invited by email; whoever may invite them does it from its Guests page.

Optional

Single sign-on

Single sign-on is provided through WorkOS. Verify your email domain first: only addresses at a domain your organization holds can sign in this way, whatever your identity provider says.

  1. Open Manage org › User Sync and, under Domain emails, choose Connect SSO.
  2. In the Admin Portal that opens, your IT administrator connects your identity provider (SAML or OIDC).
  3. People then choose Sign in with single sign-on on the login page and give their work email. Anyone new gets an account and joins at once, which adds a seat. Someone who already has an account logs in with it first, to link the two.
  • Passwords and passkeys go on working beside it: Tensorworks does not yet require single sign-on, so a misconfigured provider cannot lock your company out.
  • Someone your admins removed can still sign in to their own account, but isn't put back on your team.
  • Sign-in begins at Tensorworks, not from a tile in your identity provider.

Step 5

Connect your directory

Directory sync is provided through WorkOS, which connects Tensorworks to your identity provider or HR system. Your IT administrator connects it in WorkOS's Admin Portal, which has instructions for each provider.

  1. Open Manage org › User Sync and, under Directory sync, choose Connect a directory.
  2. In the Admin Portal that opens, pick your provider and follow its steps.
  3. Back in Tensorworks, the directory shows as Connected. Choose Sync now to read it in full right away.
  4. Under Groups, give any of the directory's groups a role: the people in it hold that role beside any of their own. People with full access need none.

Once connected:

  • Users the directory adds join the organization; people at a verified domain join at once (when they sign up, if they have no account yet), and everyone else is invited.
  • Users it deactivates or deletes are removed, freeing their seats, and an email change in the directory renames the user.
  • Directory sync manages who is on the team only. Each person signs in with their own Tensorworks account or through single sign-on, and admin status is set in Tensorworks, not by a group.
  • The organization's owner is never removed by the directory: one it lets go of stays on, managed by hand.
  • Disconnecting the directory leaves its people in place, managed by hand from then on.

Tensorworks acts on what WorkOS reports as current, never on a notification's contents alone, and an older change never overwrites a newer one.

Step 6

Bring in your agents

AI agents connect over the Model Context Protocol, signing in with OAuth or through an agent link that records who made it. Agents are users like people: limit them with roles and grants, review each one's activity, and remove one to revoke its access at once.

The General API lists what agents can do; its Quickstart connects Claude Code or Codex in a minute.

Optional

Make it look like yours

Open Manage org › Branding to put your company's logo and colors on every page, in place of Tensorworks', for everyone in your organization.

  • Upload a logo: a wide PNG, JPEG or WebP on a transparent background works best. It is scaled down to fit.
  • Choose the color behind it. The menu button turns dark on a light color.
  • Color the top bar and sidebar: pick one of the schemes offered, or set each color yourself for the light theme and the dark. Text and highlights adjust so they stay readable.
  • Hide the links and copyright line at the foot of the sidebar.

Nothing is saved until you press Save changes: until then you see your choices in a preview of both themes and in your own top bar and sidebar. Every save is kept in its History, showing who changed what. You can preview any earlier version and save it to bring it back.

Optional

Archive and monitor

The Enterprise API gives your compliance and security tools what they need, with tokens an admin makes in Manage org › API:

  • Discovery reads everything the organization holds, including edited and deleted messages and deleted files, for archiving, eDiscovery and data-loss prevention. Of the people who were on your team, it reads their sign-ins and direct messages only from while they were on it.
  • The audit log records every sign-in, with its IP address and browser, every change, with who made it and from which session, and every file opened. Admins read it in Manage org › Audit Log.
  • Event streaming, in Manage org › Event Streaming, sends the audit log to Splunk, Microsoft Sentinel or a webhook as it is written.

Reference

Billing

  • Enterprise is $500.00 per month plus $30.00 per seat per month. Seats follow your team as people join and leave, prorated, and invoices are kept under Settings › Billing.
  • Every organization is billed on its own: Pro or Enterprise lifts Free's limits in that organization alone, paid by its own card.
  • To hand an organization to someone on its team, its owner opens Settings › Organization › Ownership. It stays theirs until the new owner sets up their own billing for it (their card, for one on a paid plan) and accepts; the owner before stays an admin.
  • When Enterprise ends, the organization returns to Free. No one new joins through its domains or its directory until Enterprise returns. Everyone already in stays, and people who sign in with SSO keep doing so.

Reference

Security

  • Encryption at rest: every account, organization, project and resource seals its data with keys of its own (AES-256-GCM), so access to one never opens another. Files are encrypted in the browser before they're uploaded.
  • Access checks: every read and write is authorized on the server against the person's roles and grants.

Reference

Third-party providers

WorkOS is our provider for directory sync. When you set it up, we share your organization's name and ID with WorkOS so it can connect your directory, and WorkOS sends us the users and groups your identity provider or HR system shares with it.

Domain verification doesn't involve WorkOS: Tensorworks checks your DNS record itself.

Questions or something missing? Contact us.