Workspace Terms

1. Scope and Acceptance

These Workspace Terms govern the use of Workspaces, the shared-balance feature of Mindrift that lets several people use the platform and the API under one team account. They supplement the Terms of Service, API Terms, Privacy Policy, Data Privacy Notice and Community Guidelines, which all continue to apply. On any conflict that is specific to Workspaces, these Workspace Terms prevail. By creating a Workspace, accepting an invitation to one, or spending from one, you accept them.

Beta. Workspaces are currently offered as a beta. Features, limits and screens may change, and we may adjust or withdraw parts of the feature with reasonable notice. Beta status does not reduce any of your obligations below.

2. Definitions

• Workspace: a team account with its own balance, members, invitations, API keys, generation history and audit log.
• Owner: the member who holds the Workspace and is ultimately responsible for it.
• Member: any person with a role in the Workspace (Owner, Admin, Billing, Member or Viewer).
• Workspace Balance: prepaid funds held by the Workspace, separate from any personal wallet.
• Workspace Content: prompts, outputs and metadata produced while a Workspace pays.

3. Creating a Workspace and Limits

• Eligibility: you need a Mindrift account in good standing. If you create a Workspace for an organization, you confirm that you are authorized to bind it to these terms.
• Ownership cap: one person may own up to 3 active Workspaces.
• Size cap: a Workspace may have up to 100 seats, pending invitations included.
• Names: Workspace names must not impersonate a person, brand or Mindrift itself, and must respect the Community Guidelines.
• Fair use: creating workspaces or accounts to multiply quotas, bypass limits or evade enforcement is prohibited.

4. Roles and Permissions

Access inside a Workspace is determined by role. Roles are independent from any platform role and are enforced on our servers.

Owner

Full control: settings, members, billing, API keys, audit log, transfer of ownership and closure of the Workspace. There is exactly one Owner.

Admin

Manages members, billing, API keys and settings. Sees every generation and the audit log. Cannot close the Workspace or transfer ownership.

Billing

Adds funds and reads invoices. Cannot generate and cannot see generated content.

Member

Generates content and creates their own API keys. Sees only their own generations.

Viewer

Read-only access. Sees the whole team's generations and the balance, and cannot spend.

• Nobody can change their own role, grant a role equal to or above their own, or modify the Owner. Only the Owner can invite or appoint Admins.
• Roles are a convenience for organizing your team. You remain responsible for deciding who receives which role.

5. Shared Balance and Billing

• Top-ups: Owners, Admins and Billing members may add funds to the Workspace Balance. Top-ups are final and non-refundable, as stated in the Terms of Service.
• One-way funds: money in a Workspace cannot be transferred, withdrawn or refunded to a personal account, to another Workspace or to a member. Only usage consumes it.
• Who pays: a request is charged to the Workspace only when that Workspace is the active payer (selected in the Workspace switcher) or when a Workspace API key is used. Check the active payer before generating.
• Metering: usage is metered at the same prices as personal usage and recorded in the Workspace ledger, with the member who acted, the model and the cost.
• Spending limits: Owners and Admins may set a monthly Workspace limit and per-member monthly limits. Requests above a limit are refused. Limits are a safeguard, not a guarantee against all spend, and you remain liable for usage that occurred.
• Insufficient balance: when the balance is exhausted, generation stops until funds are added.
• Adjustments: Mindrift may credit a Workspace for service issues or goodwill. Such adjustments are recorded in the audit log with a reason.

6. Members, Invitations and Removal

• Invitations: invitations are sent by email and are valid for 72 hours. They can only be accepted by the account that uses the invited email address, and may be revoked at any time before acceptance.
• Removal and suspension: Owners and Admins can suspend or remove members who rank below them. Removing a member revokes that member's Workspace API keys. Suspending a member suspends those keys until reactivation.
• Leaving: any member except the Owner may leave at any time. The Owner must first transfer ownership to an active member.
• Ownership transfer: only the Owner can transfer ownership, and only to an active member who owns fewer than the maximum number of Workspaces. The previous Owner becomes an Admin.

7. API Keys

Workspace API keys charge the Workspace Balance and are subject to the API Terms. Keys belong to the Workspace, not to the individual who created it: Owners and Admins may revoke any key. All usage under a key is attributed to the Workspace, whoever physically sent it. Keep keys secret, rotate them on suspected exposure, and revoke keys that are no longer needed. Workspace keys are listed separately from personal keys.

8. Content, Visibility and Privacy

• Visibility: Workspace Content generated while a Workspace pays is visible to the Workspace according to role: Members see their own, while Owners, Admins and Viewers see the whole team's. Do not generate content you are not comfortable sharing with your team's administrators.
• Notice to team members: if you invite people, you are responsible for informing them that their Workspace activity is visible to the Workspace and recorded in its history and audit log.
• Ownership of outputs: rights in outputs are governed by the Terms of Service. Within your organization, who owns what is a matter between you and your Members.
• Personal data: we process Workspace data as described in the Privacy Policy and Data Privacy Notice. Where you upload or generate content that contains other people's personal data, you are responsible for having a lawful basis to do so.
• Moderation: the Community Guidelines and safety systems apply to every request. Violations by any Member can lead to restrictions on that Member, on the Workspace, or on both.

9. Security and Audit

• Two-factor authentication: privileged roles (Owner, Admin, Billing) are expected to use 2FA. It is required by default for sensitive actions and may be re-requested before them.
• Audit log: membership changes, role changes, invitations, key events, billing actions and administrative actions are recorded with the actor, the target and, where available, the IP address. The log is visible to Owners and Admins and is kept for security, accountability and legal compliance.
• Your duties: protect your account, review who has access, and remove people who no longer need it. Mindrift is not responsible for losses caused by credentials or keys that you or your Members failed to protect.

10. Closing a Workspace

The Owner may close a Workspace once its balance is spent. Closing revokes every Workspace API key, cancels pending invitations and ends access for all Members. Because funds cannot leave a Workspace, a Workspace that still holds a balance cannot be closed by the Owner; contact support to discuss the remaining balance. Closure cannot be undone.

11. Suspension and Enforcement by Mindrift

Mindrift may suspend a Workspace or a Member, revoke keys or close a Workspace for non-payment, security risk, abuse, fraud, violations of our policies or legal compulsion, with or without prior notice proportionate to severity. While a Workspace is suspended, its balance remains in place but cannot be spent. Termination for cause forfeits the remaining Workspace Balance in accordance with the Terms of Service. Platform administrators may take support and safety actions on a Workspace (for example adding or removing a member, or crediting the balance); every such action is recorded in the audit log.

12. Responsibility and Liability

The Owner is responsible towards Mindrift for the Workspace, for amounts spent from it and for the conduct of its Members. Workspaces are provided as is, and liability for them falls under the as-is and liability-cap provisions of the Terms of Service. To the extent permitted by law, Mindrift is not liable for decisions about roles, limits or access that you make inside your Workspace, or for disputes between you and your Members.

13. Changes and Contact

We may update these Workspace Terms as the feature evolves. Material changes will be announced in the console or by email, and the date at the top of this page will change. Continued use after the effective date means you accept the updated terms. Questions: [email protected].