Agency workspaces

What the Agency screen shows

The Agency screen is available from the sidebar only when the current workspace is an agency parent. Its main view is named Clients. It reports the number of clients and the number that need attention, and it gives you a Search clients field when the roster is not empty.

Each client entry represents a client workspace. Opening a client switches the active workspace to that client workspace, so subsequent work is performed in the selected client boundary rather than in the agency parent. Check the current workspace after switching before creating data, changing a setting, or starting an execution.

Read client status before switching

Each visible client row contains the client name and a LinkedIn token health label. The available labels are Connected, Expiring, Expired, and Not connected. The screen pairs the label with a visible marker, so the status is not conveyed by color alone.

A roster row can also be marked as needing attention. That is a triage signal, not a statement that work has been completed or that a message was delivered. Open the client workspace and inspect its current state before deciding how to respond to a token or publishing signal.

The roster response includes the client workspace identifier, client status, token health, a pending count, a last-published timestamp, a posts-this-week value, a cadence update timestamp, and the needs-attention flag. The Agency screen itself is deliberately a lightweight roster and launcher, so use it to choose the client workspace and then inspect the relevant client surface.

Posts this week is a trailing seven-day value in the roster data. It can be stale for up to seven days, and the cadence update time indicates when that status was updated. Use the value as a prompt to inspect the client’s current publishing state, not as a substitute for the client’s own records.

Add or claim a client workspace

The empty state offers two distinct actions. Create new client provisions a new client workspace. Claim existing workspace adds an already existing client workspace to the agency roster. They should not be treated as interchangeable because one creates a workspace and the other changes the relationship of an identified workspace.

The app asks for a client name when you create a client. When you claim an existing workspace, identify the target client workspace and enter the confirmation name required by the claim form. The roster is refreshed after either change, so the visible client list is the first place to verify the result.

1. 1

   Open an agency workspace

   Select Agency in the sidebar and confirm that the workspace is an agency workspace. The screen shows a Clients heading and the current client and attention counts.
2. 2

   Inspect the client roster

   Use Search clients when the roster already has entries. Open a client only after checking its displayed name, then confirm the active workspace after the switch.
3. 3

   Create or claim the intended client

   Use Create new client for a new workspace. Use Claim existing workspace only when you have identified the existing client workspace that should join the agency roster.
4. 4

   Check the receipt in the app

   Return to Clients and confirm that the roster shows the expected client. If provisioning is incomplete, keep the client name and workspace identity available for follow-up rather than treating a missing row as a completed change.

Confirm the roster change

A successful new-client operation returns a client workspace identifier and a provisioning state. The provisioning states are provisioning, billing_pending, and active. A client can appear in the roster while provisioning is still progressing, so the name alone is not evidence that every client service is ready.

The Add Client dialog disables the create control until a non-empty client name is supplied. It disables the claim control until both a client workspace identifier and the exact workspace name are supplied. These checks prevent an empty form submission, but they do not identify the correct workspace for you.

After a create or claim action, the app refreshes the roster. Check the returned client workspace against the row that appears. If you intended to manage an existing workspace, confirm that the target workspace identifier and the typed name refer to the same workspace before you submit the claim.

Creating a client provisions it under the agency and bills it on the agency plan. Claiming an existing workspace immediately cancels that workspace’s current subscription and re-bills it under the agency. Read the dialog text, target identifier, and target name carefully because this effect cannot be undone from the claim flow.

Work across client boundaries carefully

An agency plan groups client workspaces under one account. The Agency screen is a roster and switching surface, not a shared store for every client fact. A client workspace remains the place where its workspace work is visible after you open it.

Keep durable positioning, decisions, and source-backed knowledge in that workspace’s Context. Keep provider credentials in Integrations. Keep membership and organization configuration in workspace settings. This separation makes it clear which client owns a fact, a connection, or a collaborator relationship.

Keep agency triage separate from client work

The roster gives an agency operator a compact way to find client workspaces. It does not merge the underlying client records into a single workspace. A client’s Context, connections, and work remain scoped to the client workspace after you open it.

The attention count is useful for choosing where to look first. It does not explain the cause of the signal. An expired LinkedIn token, a publishing gap, and a client workflow question need different checks in the selected client workspace.

Search filters the loaded roster by client name. It does not discover workspaces outside the agency roster. If a client workspace is not in the roster, use the agency relationship controls only after you have identified the intended workspace.

The roster can show a last-published timestamp or no timestamp when a client has never published. Treat that absence as an observed roster value. It does not establish why no post exists, whether a draft is scheduled, or whether a provider is connected.

When you need to work on a client result, open that client first and use the product surface for the result itself. For example, use Context for durable knowledge and the client’s connection settings for provider state.

When it goes wrong

If the app says This workspace is not an agency, switch to the agency parent workspace. The roster does not load for a non-agency workspace. If the client list fails to load, the screen shows the returned error instead of a roster. Preserve the active workspace identity and retry after the workspace connection is available.

If Search clients returns No clients match, it means the loaded roster has no client name matching the entered text. Clear the query or use the spelling shown in the roster. Do not create a second client merely because a search has no result.

If a client row is absent after a create or claim action, treat the result as incomplete until the roster refresh shows the workspace. The client service also treats a completion without a client workspace receipt as an error. Check the workspace identity and client name before retrying, so a retry does not attach the wrong workspace.

Use workspaces, members and roles when the problem is organizational access rather than the client roster. Use Context when the missing item is a client fact or decision rather than a client workspace relationship.