Workspaces

What lives in one

Documents and tables, and nothing else. The workspace has two views: its files, which is everything uploaded to it, and its tables, which is every question you have asked of those files. A table can only see documents in its own workspace.

Because access is granted per workspace, one workspace is one audience. If a set of documents should be visible to a different group of people than another set, those are two workspaces even when the work is related.

Creating one

Whether you can create a workspace is governed by your role in the organisation, not by anything workspace-level — for the obvious reason that there is no workspace yet to hold a permission. See team and roles.

A new workspace is private to you. Organisation admins hold Manage on every workspace implicitly; nobody else can see it until a sharing rule reaches them.

Settings

The general tab holds four things worth knowing about:

• Name. Editable, and it should be unique — the workspace switcher and the usage breakdown both identify a workspace by name, and two called “Q3” are indistinguishable in both.
• Created by and created on. Fixed, and useful for exactly one question: whose workspace this was before it was shared.
• Workspace ID. A copyable reference. It is what support will ask for.
• Archive. Reversible — see below.

The access tab is where sharing rules live, and it is covered separately in sharing a workspace. Editing any of this needs Manage on the workspace.

Archiving, and the checkbox to read twice

Archiving takes a workspace out of the way. It becomes read-only — the name cannot be edited and the tables cannot be changed — and it can be restored later, which makes it the right end state for finished work where the table is still the record of what was found.

The archive dialog also offers to delete every document in the workspace, and that checkbox is ticked by default. Restoring the workspace does not bring those documents back, and re-uploading them means paying to read them again. This is why the dialog asks you to type the workspace name to confirm: archiving with the box ticked is the most destructive thing in the settings modal. Untick it if you want the work kept.

Nothing about archiving reclaims credits. The reading was paid for at upload and does not come back; equally, an archived workspace does not accrue anything.

API keys

A workspace can hold API keys, created with a label and an expiry of 30, 60 or 90 days or never, under the same Manage level as its other settings. A key is shown once, at creation, and stored hashed — if you lose it, you create another. Programmatic use is not covered in these docs yet.

A workspace key is scoped to this workspace, which is the difference between it and a personal key — a personal key belongs to a person and reaches every workspace that person can, and is created from account settings rather than from here.