Workspaces

Use the workspace menu above Overview in the sidebar to choose where you work. Connections, uploads, drafts, scheduled posts and publish history belong to the selected workspace.

​

Default workspace

Every installation starts with Default. Everyone on the team can access it using their existing team role. Default cannot be deleted. When you upgrade an existing installation, its accounts and content remain together in Default.

​

Create a workspace

Administrators can open the workspace menu and choose Create Workspace. Enter a name and description, then choose Create workspace. The new workspace is selected and its creator is added immediately. A workspace only appears in the menu for people who have access to it. Being a team administrator does not give someone access to every workspace’s accounts or content.

​

Manage details and access

Select a non-default workspace, then open Workspace Settings:

• Audit Logs records workspace access, connections, drafts, media, publishing and workspace API key changes. Administrators with workspace access can filter the history and inspect each event.
• General lets administrators with access update its name and description.
• Manage Access lets those administrators add existing team members or remove them immediately. There is no separate invitation to accept.

Choose Add members, open the Member dropdown, search by name or email, select one person and choose Add member. The modal closes after they are added. Open it again to add another person. People keep their team roles. An administrator added to a workspace can manage it; members can compose and publish; viewers can read. Members cannot leave a workspace themselves. An administrator with access can remove another person or themselves.

​

Review all workspaces

All team administrators can open Team Settings → Team → Workspaces to see the workspace directory and member counts. Choose View members to open the member list. Viewing this directory does not grant access to a workspace’s content or settings.

​

Delete an empty workspace

An administrator with access can delete a non-default workspace from Workspace Settings → Danger Zone → Delete workspace when it has no connected accounts, uploads, drafts, posting history or scheduled posts. Finish or abandon any in-progress account connection first. Removing members is not required to make a workspace empty. Default cannot be deleted.

​

Connect scripts and assistants

Personal API keys and MCP connections follow their owner’s workspace memberships. Shared automation uses workspace API keys, which administrators create under Workspace Settings → API Keys for the selected workspace, including Default. Those keys cannot access a different workspace. Clients first list available workspaces, then include the chosen workspaceId on publishing actions, including for Default. See API keys, MCP connections and request conventions for examples.

​

Audit history

Open Workspace Settings → Audit Logs to see who changed a resource and when, including activity from API keys, MCP clients and the publishing worker. Filter by event, resource, actor or time; results update as you make changes. Use the search button to refresh the current filters, then choose Details to inspect an event. Default has its own audit history as well. Events begin after upgrading to a version with audit logging; earlier activity is not reconstructed. Posted records resource IDs and safe event metadata, without post text, media contents, passwords or tokens. Failed or rolled-back changes are not recorded as completed changes. Audit events cannot be edited or deleted through the application.