Summary and recommendation
Tettra user management can be run manually, but complexity usually increases with role models, licensing gates, and offboarding dependencies. This guide gives the exact mechanics and where automation has the biggest impact.
Tettra is a knowledge base platform built around a fixed three-role model - Admin, Member, and Guest - applied at the workspace level.
Page and category visibility can be restricted per user or group, layering content-level access control on top of the workspace role.
There are no custom roles, and role granularity does not extend beyond these three tiers.
Quick facts
| Admin console path | Settings → Members |
| Admin console URL | Official docs |
| SCIM available | Yes |
| SCIM tier required | Professional |
| SSO prerequisite | Yes |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Admin | Full access to all settings, can invite and remove users, manage billing, create and edit all pages and categories, manage integrations, assign roles. | Any paid plan | Counts as a paid seat | There must always be at least one Admin on the account; the last Admin cannot be removed. | |
| Member | Can create, edit, and view pages and categories they have access to; can suggest edits; can use Q&A features. | Cannot access billing settings, cannot manage users or roles, cannot change workspace-level settings. | Any paid plan | Counts as a paid seat | 10-user minimum applies on Basic and Scaling plans. |
| Guest | Read-only access to specific pages or categories they are explicitly granted access to. | Cannot create or edit content, cannot access pages outside their granted scope, cannot manage any settings. | Guest availability and seat cost relative to paid seats is not explicitly documented in currently verifiable official sources. |
Permission model
- Model type: role-based
- Description: Tettra uses a fixed set of roles (Admin, Member, Guest) applied at the workspace level. Page and category visibility can be restricted to specific members or groups, providing content-level access control on top of the role layer.
- Custom roles: No
- Custom roles plan: Not documented
- Granularity: Workspace-level roles with page/category-level visibility controls; no custom role creation.
How to add users
- Navigate to Settings → Members in the Tettra app.
- Click 'Invite Members'.
- Enter the email address(es) of the user(s) to invite.
- Select the role to assign (Admin or Member).
- Click 'Send Invite'. Invitees receive an email to join the workspace.
Required fields: Email address, Role (Admin or Member)
Watch out for:
- Invitations are email-based; users must accept the invite to activate their seat.
- 10-user minimum seat count is enforced on Basic and Scaling plans regardless of actual active users.
- SCIM-based provisioning (Okta, Azure AD) is only available on the Professional plan ($7,200/year, 50-user minimum).
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | No | Not documented |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | Yes | Professional ($7,200/year, 50-user minimum) |
How to remove or deactivate users
- Can delete users: Unknown
- Delete/deactivate behavior: Official Tettra documentation describes removing users from the workspace (which revokes access), but does not explicitly distinguish between a permanent delete and a deactivate/suspend state in currently verifiable public documentation. Removal via SCIM deprovisions the user automatically on the Professional plan.
- Navigate to Settings → Members.
- Locate the user to remove.
- Click the options menu (⋯) next to the user's name.
- Select 'Remove from team' and confirm.
| Data impact | Behavior |
|---|---|
| Owned records | Pages and content created by the removed user remain in the workspace and are not deleted. |
| Shared content | Content the user contributed to remains accessible to other members. |
| Integrations | If the user was connected to Slack or other integrations at the personal level, those personal connections are severed upon removal. |
| License freed | Removing a user frees the seat, though the 10-user minimum on Basic and Scaling plans means billing may not decrease below that floor. |
Watch out for:
- Content authored by a removed user is retained in the workspace.
- On Basic and Scaling plans, removing a user below the 10-user minimum does not reduce the billed seat count below 10.
- SCIM deprovisioning on Professional plan automates removal when the user is deactivated in the IdP.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Basic seat | Core knowledge base features; 10-user minimum; limited integrations | $4/user/month (annual) or $5/user/month (monthly) |
| Scaling seat | Additional features over Basic; 10–250 users | $8/user/month (annual) or $10/user/month (monthly) |
| Professional seat | SSO, SCIM provisioning, priority support; 50-user minimum included in base price | $7,200/year (first 50 users included) |
- Where to check usage: Settings → Members (shows current member list and count)
- How to identify unused seats: No built-in last-login or activity report is documented in currently verifiable official sources; admins must manually review the member list.
- Billing notes: Basic and Scaling plans enforce a 10-user minimum; billing does not decrease below this floor even if fewer users are active. Professional plan is a flat annual fee of $7,200 covering the first 50 users; additional seats above 50 are billed separately. SSO and SCIM are exclusive to the Professional plan.
The cost of manual management
User lifecycle in Tettra is managed through Settings → Members at https://app.tettra.co/teams/settings/members. Invitations are email-based, and a seat is not activated until the invitee accepts. Removing a user revokes access and retains their authored content, but official documentation does not distinguish between a permanent delete and a suspended state.
License overhead compounds the manual burden. Basic and Scaling plans enforce a 10-user minimum, so billing does not drop below that floor even if fewer users are active.
There is no built-in last-login or activity report, meaning admins must manually audit the member list to identify unused seats - a gap that affects every app in a portfolio at scale.
SCIM-based provisioning is gated behind the Professional plan ($7,200/year, 50-user minimum, annual billing only), and SSO must be fully configured before SCIM becomes available. Teams on Basic or Scaling plans have no programmatic provisioning path.
What IT admins are saying
Community evidence is not specific enough to quote or summarize yet for this app.
The decision
Tettra's manual provisioning workflow is straightforward for small, stable teams but does not scale cleanly. The lack of an activity report means seat hygiene requires ongoing manual effort, and the 10-user billing floor creates a fixed cost regardless of actual headcount.
Teams that need automated lifecycle management must commit to the Professional plan, which carries a significant annual minimum.
If your organization already runs Okta or Azure AD and can justify the Professional tier, SCIM provisioning removes the manual overhead for every app in your stack that supports it. If not, plan for recurring manual audits to keep the member list accurate.
Bottom line
Tettra's user management is functional but lean: a fixed role model, email-based invitations, and no built-in activity reporting mean that seat hygiene depends entirely on manual admin effort.
The 10-user billing minimum on lower tiers adds cost pressure for small teams, and automated provisioning is locked to the Professional plan at $7,200/year. Teams willing to meet that threshold and already operating Okta or Azure AD will get clean, IdP-driven lifecycle management;
everyone else should budget time for regular manual audits.
Automate Tettra workflows without one-off scripts
Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.
