Workspaces in the provider console

In short

The Workspaces page lists every institution in this region. You can search it, filter it by status and plan, create a workspace, and open one to see its overview, its health in numbers and what it used each month. None of this shows what the workspace holds.

The list

Column	What it shows
Workspace	Name and slug. A scheduled deletion shows as Deletion and its date
Status	Active, Suspended or Closed (closed by a move to another region)
Plan	The plan’s name, Over limit when the workspace is over what was agreed, and AI calls requested when its administrators have asked for more AI assistant calls this month and nobody has answered (a request from an earlier month has expired and isn’t counted). See Adding calls for a month
Users	People who can sign in (active and invited), with the share of the agreed number when one was agreed
Last activity	When someone last signed in, or Never
Created	When the workspace was created

Search by part of the name or slug, and filter by status or plan. Every time the list is read, the audit log records it, with the search and filters used.

When workspaces have been deleted after their scheduled date, the page also offers Deleted workspaces: what is kept of each. See What is kept.

How to create a workspace

You need the Owner or Operations role.

1. On Workspaces, select Create workspace.
2. Under Institution, enter the Name and a Slug. The slug is what people type at sign-in: 2 to 63 lowercase letters, digits or dashes, starting with a letter or digit.
3. Choose the Type of institution and enter the Country as a two-letter code, such as GH or CI.
4. Optionally enter the Base currency, Time zone and Jurisdiction. Left empty, each takes the jurisdiction’s value, and the jurisdiction takes the country’s.
5. Under First administrator, enter their Email and Name.
6. Under Plan and agreed limits, enter the plan and any limits. Left alone, the plan is standard with no limits. AI assistant calls per month is optional: leave it empty for the installation’s default, or enter 0 when the plan doesn’t include the assistant on your key. See Plans and limits.
7. Select Create workspace.
8. Copy the administrator’s Temporary password and pass it to them over a channel you trust.

The temporary password is shown once

It is not sent by email and can’t be displayed again. It works for 72 hours and must be changed at the first sign-in. If it is lost, an operator issues another with speculapro tenant reset-password.

Creating a workspace here does exactly what speculapro tenant create does: the built-in roles, the first administrator, the jurisdiction’s defaults and, on a multi-region service, the slug’s reservation in the global directory. The new workspace is pinned to this console’s region.

Message	Meaning
a workspace with that slug already exists (in this or another region)	The slug is taken. Slugs are unique across every region
the workspace’s details were refused: check the slug, kind, country and currency	One of those values isn’t valid
The workspace was created, but the global directory does not list it yet. Run speculapro cell sync.	The workspace exists and the password shown is good, but the directory couldn’t be updated. Run the command; see Running more than one region

A workspace’s page

Opening a workspace is recorded in the audit log each time. The page has five tabs.

Tab	Shows	Needs
Overview	About the workspace, and its health	workspaces.view
Usage	Transactions and real-time decisions per month, and AI assistant calls and tokens	usage.view
Plan & limits	The plan, agreed limits and staff notes	plans.view, and plans.manage to change
Actions	Suspend, reactivate, schedule or cancel deletion	changes.view, and changes.request to propose
Support access	Requests for this workspace, and asking for access	support.view, and support.request to ask

Overview

About this workspace lists its status, plan, type, country, base currency, time zone, jurisdiction, region, how many users it has and how many have signed in at least once, the last sign-in, when it was created and its ID.

When the workspace is suspended, a banner says since when and the reason that was given. When a deletion is scheduled, a banner says for when and where it stands.

Health

Health is numbers about the workspace’s pipeline: when and how many, never what.

Line	What it tells you
Latest transaction	When the latest transaction happened at the institution
Received	When it arrived at SpeculaPro
Time to arrive	The gap between the two. A growing gap means the institution’s feed is running late
Latest real-time decision	When the workspace last asked for a decision
Webhook deliveries failed in 24 hours	Deliveries that failed
Webhook deliveries overdue	Deliveries due more than 15 minutes ago
Notifications failed in 24 hours	Emails and messages that could not be sent
File loads failed in 24 hours	File imports that failed
Scheduled rules failing	Scheduled rules that keep failing and are retried with a delay

Each count shows Fine at zero and Check above it, and the panel’s header sums them: No problems, or the number of things to check.

Usage

Choose 6, 12 or 24 months. The chart and the table show, per calendar month:

• Transactions received,
• Real-time decisions made,
• the Busiest day for transactions,
• and, when a monthly limit was agreed, the share of it used.

Above them: transactions and decisions this month, and Users today against the agreed number. Export CSV downloads the table.

How usage is counted

The worker counts once an hour, so figures can be up to an hour old; the page says when they were last counted. Months are calendar months in UTC. Storage is not measured per workspace.

AI assistant usage

Under the monthly figures, the AI assistant panel shows what the workspace’s AI assistant was used for, from the provider’s own record.

• The line under the title gives the plan’s allowance: 500 calls a month agreed on the installation’s key., No allowance agreed: the installation’s default applies. or Not in this plan: the workspace can only use its own key. Set it under Plan & limits.
• The table has one row per Month, Key and Model, with Calls, Tokens read and Tokens written. Key is Installation’s (billable) for calls made on your key, or Workspace’s own for calls on the institution’s key, which the model’s provider bills to the institution; those are shown for reference.
• Export CSV downloads the rows (month, key, model, calls, input_tokens, output_tokens).
• When nothing has been asked yet: The assistant has not been used.
• Below it, More AI calls lists the workspace’s requests for more calls and lets you add calls for the current month. See Adding calls for a month.

The calls in the picture were made against a local test stand-in for the model’s provider.

What this record is, and isn’t

• Counts only. The record holds a workspace’s ID, the month, what the assistant was asked to do, the model, whose key, and the numbers of calls and tokens. Nothing of what was asked or answered, and nobody’s name. The panel adds the features together.
• Unlike the monthly figures above, it isn’t counted hourly: it is updated as each call is counted, and the months selector applies to it too.
• It is kept when the workspace is deleted, so that the last month can still be accounted for. A deleted workspace has no page in the console, though: after deletion the figures can be read only in the database (provider_ai_usage, by the workspace ID on its tombstone).
• No prices. Nothing here computes a cost or an invoice.
• A move between regions splits it. The record stays in the region where the calls were counted. After a move the target region’s record starts from the move and counts only the calls made there, so the two regions’ figures for the month of the move add up to the workspace’s total. (Before migration 00073 the target showed that month’s whole count; figures copied then are not corrected.)

Related

• Plans and limits
• Suspending and deleting a workspace
• Support access
• Provider console API