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
Getting started
Step 1
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.
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
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.
example.com) and choose Add domain.You can verify several domains. Each belongs to one organization at a time.
Name: _tensorworks-verification.example.com
Type: TXT
Value: tensorworks-verification=<token>Step 3
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.
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
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.
| Access | Allows |
|---|---|
| Owner | The person who made the organization, or took it over. Runs it like an admin, alone manages its billing, and is always on its team. |
| Admin | Runs 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 access | Works in everything, as the organization's owner would, including creating, renaming and archiving projects. |
| Limited | Opens 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 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.
Step 5
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.
Once connected:
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
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
Open Manage org › Branding to put your company's logo and colors on every page, in place of Tensorworks', for everyone in your organization.
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
The Enterprise API gives your compliance and security tools what they need, with tokens an admin makes in Manage org › API:
Reference
Reference
Reference
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.