Home/Business OS/Team Accounts
Team Accounts · Scale

Give everyone access. Give no one too much.

The moment a company is more than one person, the shared login becomes a liability: no idea who did what, and everyone can touch everything. Team Accounts gives each person their own login, a role, and access scoped to exactly the entities they should see, with an audit trail on every action.

Unlimited seats Role-based access SSO & audit log
Live product

Pick a role, see exactly what it can touch.

This is the permission matrix. Switch between the four roles and watch access change across every part of the OS, from filings to billing. What a person can do is never a guess.

access · role permissions Admin
Filings & Compliance
Business Banking
Books & Finance
Cap Table
Document Vault
Team & Billing
Every action a role takes is written to an immutable audit log. Access can also be scoped by entity or region
Why it exists

The shared login is a habit that eventually bites.

Almost every small company starts with one login that gets passed around. It's convenient right up until it isn't: no record of who filed what, a bookkeeper who can see the cap table, a departed contractor whose access nobody can cleanly revoke without resetting a password for the whole team.

As the company grows, that convenience turns into real exposure. Sensitive things, ownership, banking, billing, sit behind the same door as routine ones, and "everyone can do everything" is exactly the finding an auditor or a security review flags first. The fix isn't locking people out; it's giving each person the right door.

Team Accounts gives everyone their own login and a role that scopes what they can see and do, right down to specific entities or regions. Every action is attributable, adding and removing people is instant, and on enterprise it plugs into your identity provider, so the OS follows the same access rules as the rest of your stack.

How it works

Invite, assign, scope, audit.

Setting up access is a few minutes of work that saves a security headache later.

01Invite the personAn email invite goes live in about 30 seconds; no shared password to hand around.
02Assign a roleOwner, Admin, Member, or Viewer sets the baseline of what they can do across the OS.
03Scope the accessNarrow them to specific entities, states, or clients, so they see only their slice.
04Everything loggedEach action is written to an immutable audit log, ready for a reviewer or auditor.
What you get

Access control that a security review passes.

Unlimited seatsAdd your whole team, contractors, and read-only viewers with no per-seat charge on the subscription.
Four clear rolesOwner, Admin, Member, Viewer, each with a defined baseline, so no one has more access than they need.
Scoped by entityLimit a person to specific entities, states, or clients, so a regional manager sees only their region.
Immutable audit logEvery filing, document view, and role change is timestamped and attributed, ready for an auditor.
SSO & SCIMSign in with Okta, Azure AD, or Google over SAML, with automatic provisioning on enterprise.
Instant offboardingRemove someone and access is revoked immediately, with no shared password for the team to reset.
FAQ

Team accounts, answered.

How many seats do I get?
Unlimited on the Compliance Subscription, with no per-seat charge. Add your whole team, your contractors, and read-only viewers without watching a seat count, so access is never a reason to keep sharing one login. The cost of adding a person is zero, which is exactly how it should be.
What are the roles?
Four: Owner, Admin, Member, and Viewer. The Owner has full control including billing, an Admin manages the team and filings, a Member files and edits, and a Viewer has read-only access. The matrix above shows exactly what each role can touch across every part of the OS, so the baseline is never ambiguous.
Can I limit who sees which entity?
Yes. On top of the role, you can scope a person to specific entities, states, or clients, so a regional manager sees only their region and a contractor sees only the entities you share. Everything else stays hidden, which is what makes it safe to give outside people access at all.
Is there an audit trail?
Yes. Every action, from a filing to a document access to a role change, is written to an immutable audit log with a timestamp and the person who did it, ready to hand to a security reviewer or an auditor. When someone asks "who changed this?", the answer is a lookup, not an investigation.
Do you support SSO and SCIM?
Yes, on the enterprise tier. Sign in with Okta, Azure AD, or Google over SAML, and SCIM provisions and deprovisions users automatically as your directory changes, so access to the OS follows the same lifecycle as the rest of your tools. See SSO for the setup.
How fast is adding or removing someone?
Adding a teammate is an email invite that goes live in about 30 seconds. Removing one is instant and clean: their access is revoked immediately, with no shared password for the rest of the team to reset, and their audit history stays intact. Offboarding stops being the security gap it usually is.
What does it cost?
Team seats and role-based permissions are included with the Compliance Subscription, with no per-seat charge. SSO and SCIM are on the enterprise tier. See the pricing page or talk to sales for enterprise access needs.

Retire the shared login for good.

Give every person their own access, scoped to what they should see, with an audit trail on everything, at no per-seat cost.

Unlimited seats Role-based Audit log
Team AccountsSet up →