Workspaces

A workspace holds templates, themes, credits, billing, and storage settings. Templates can be shared with the workspace or kept private by their creator. Your user account identifies who performs an operation and owns its output files. You can belong to several workspaces with a different role in each.

This guide describes the workspace release. Creating workspaces and sending invitations require collaboration to be enabled for the deployment.

Roles and file access

All access stays within the selected workspace. Template capabilities apply only to templates you can access; admins cannot access another member’s private templates. Admin access to one workspace does not grant access to another. Files created by an admin still belong to that admin, including outputs derived from another member’s file.

Consumers can generate PDFs from their own HTML or data through metered API/MCP operations. They cannot use free authoring previews or persist template changes. A published template uses its published structure, theme, and asset snapshot; an unpublished template is unavailable to consumers. An editor’s private template chat history is not shared with other editors.

Template sharing

Editors and admins choose sharing when creating a template:

• All in workspace is the default. Editors and admins can author the template, and consumers can use its published version and previews.
• Just me keeps the template accessible only to its creator, including its assets, previews, and version history. Other members, including admins, cannot access it.
• Selected users shares with the workspace members you choose. The creator always retains access. Selected consumers see published content and previews; selected editors and admins can also edit. Members outside the selection have no access, including admins.

The creator can change Sharing and its selected users in the template editor. Other editors can edit a shared template but cannot change its owner or audience. Sharing changes apply immediately to both draft and published access; publishing and rolling back do not change sharing. Duplicating creates a template owned by you and preserves the sharing choice and selected users who are still workspace members. Choosing no users limits access to the creator.

Private templates still belong to their workspace. Their creator needs an active membership and the appropriate role to use them. A creator with the consumer role can use a private template’s published version, but cannot edit it or access its draft. Existing templates remain shared with the workspace after this change.

Template sharing does not change file access or billing. PDFs generated from private templates spend workspace credits and follow normal file ownership: their creator can access them, and workspace admins can access all stored workspace files.

Select a workspace

Use the workspace selector in the dashboard sidebar. The selected workspace controls the dashboard’s files, templates, usage, settings, and balance. Selection is local to the browser tab, so separate tabs can use different workspaces.

Save pending edits before switching, or confirm that you want to leave them. Switching reloads workspace screens. Changes to your membership or role also refresh access when detected.

API keys and OAuth connections work differently: each is permanently bound to the workspace chosen when it was created or authorized. Switching the dashboard does not change existing integrations or their billing destination.

Invite and manage members

An admin opens Workspaces, enters an email address, selects a role, and sends an invitation. Invitations expire after seven days. Resending replaces the previous invitation token; an admin can also revoke a pending invitation.

Open the invitation and sign in with its recipient email address. The address must be verified. Login preserves the invitation so you can accept it after verification. Joining a workspace does not move your personal workspace’s content or credits.

Admins can change roles or remove members from Workspaces. Members can leave, but the final admin must appoint another admin first. Removal revokes that member’s workspace credentials. Rejoining requires new credentials; it does not reactivate old keys or connections. Removed members’ files remain available to workspace admins until their normal deletion or retention rules apply.

Credits, billing, and storage

PDF and AI operations spend the bound workspace’s credits. Every member can see the available balance; only admins manage purchases, billing details, payment settings, and coupons. If you are an editor or consumer and credits run out, ask an admin to add more.

Monthly limits per member

By default, every member has unlimited monthly use of the workspace’s available credits. An admin can set a Monthly credit limit under Workspaces → Members, including for themselves or another admin. Enter a non-negative number with up to two decimal places. Leave the field blank to remove the limit; 0 blocks paid operations without blocking free operations.

Each member’s limit covers their net charged usage across REST requests, MCP connections, API keys, and paid AI requests in that workspace. The period is a calendar month in UTC and resets at 00:00 UTC on the first day of the next month. Unused allowance does not roll over. Refunds reduce usage in the original charge’s month; a refund for an earlier month does not add allowance to the current month.

Changes apply immediately and count usage already charged during the current month. Lowering a limit below the member’s usage leaves no remaining allowance and blocks further paid use. Raising or clearing it allows further use when workspace credits are available.

Admins see each member’s limit, usage, remaining allowance, and reset time. Every member can see their own allowance on the dashboard and workspace page. An allowance does not reserve or add credits: requests still draw from the shared workspace balance. If a monthly limit blocks a request, ask an admin to change the limit or wait for the reset; buying workspace credits does not change a member’s limit.

Storage settings

Storage mode, retention, and BYOB bucket configuration belong to the workspace. Omitted storage options use workspace defaults. Set storage.mode in REST or storage_mode in MCP when a workflow requires a specific result, such as an in-memory PDF. Changing the current bucket does not move previously stored files. See Storage modes.

Template assets follow the template’s sharing choice. Uploading an image or saving a private document crop as an asset makes it available to everyone who can access that template’s relevant draft or published version. Check the workspace and destination template before doing so. URLs already issued may remain usable for up to five minutes after access changes.

Connect an integration

Create an API key while the intended workspace is selected, or choose that workspace on the OAuth consent screen. Every request acts as the credential’s creator, with their current role and the granted OAuth scopes. A conflicting X-Workspace-Id header is rejected; it cannot retarget a key or connection.

Members manage their own keys and connections. Admins can inspect safe credential metadata and revoke credentials belonging to anyone in the workspace. They cannot recover another member’s key or act as that member.

Dashboard session requests use explicit workspace context on supported management and preview routes. A dashboard login token does not replace an API key or OAuth token for metered PDF endpoints. See Authentication and MCP server.

Existing accounts

During migration, each existing user receives a personal workspace named from their account and becomes its admin. Existing content, credits, billing associations, and storage configuration move into that workspace. Resource IDs and existing physical file locations are preserved. Existing keys remain associated with that migrated workspace; older OAuth clients may need to reconnect when prompted.