Concepts
LiveWorkspaces, members, and access
How Fygment scopes Skills, members, invites, approvals, reports, and billing to one workspace.
- Audience
- Workspace owners, admins, and teammates joining a Fygment pilot.
- Updated
- 2026-05-20
A workspace is the unit of trust in Fygment. Membership, role, invite, install, report, and billing behavior all resolve through that boundary.
Workspace model
Users are global, but customer data is workspace-scoped. Skills, versions, proposals, install records, OAuth MCP connections, support reports, and billing state belong to the active workspace.
Owners and admins manage members, invites, join requests, policies, approvals, and billing actions. Members can use the workspace surfaces they are allowed to see, but mutating governance actions stay server-authorized.
Invite a teammate
- 1
Open workspace settings
Use the workspace shell settings page and choose Members.
- 2
Send an invite
Enter the teammate email and role. Existing active or disabled members are rejected before invite tokens are created.
- 3
Let the invitee sign in from the invite link
Invite acceptance sets the invited workspace as default and audits the first successful acceptance.
Access checks
A teammate lands on onboarding instead of the workspace.
Check: Confirm they used the invite link and signed in with the invited email address.
Next: Revoke and reissue the invite if the original link expired or was accepted by another account.
A company-domain user cannot see private workspace details.
Check: This is expected before owner/admin approval.
Next: Have an owner/admin approve the verified-domain join request or send a direct invite.
Related docs
- Get started with Fygment
Start here when you need the shortest path from sign-in to a workspace that can import, review, install, and check governed AI Skills.
- Review and approve Skills
Governance is the difference between a shared Skill library and a loose pile of files. Review decisions decide what can be installed and trusted.
- Billing and launch mode
Public launch uses a workspace effective tier: Solo remains free for the local creator loop, Advanced / Teams unlocks paid collaboration and external import actions, and Enterprise stays support-managed.