Skip to main content

Workspaces

A workspace is an organisation's space in Pollinator. Every activity, session, result, integration, API key, webhook and audit record belongs to exactly one workspace, and nothing is visible from another. A request always acts in the workspace of the person or key making it; it can never name a different one.

Personal and organisation workspaces​

  • Personal. Created automatically when someone creates their account by signing in, named after them, with them as its owner. A personal workspace is fully usable on its own: Pollinator works standalone with no set-up.
  • Organisation. A shared workspace for a team or company. It is created through the workspace API (POST /api/v1/workspaces), and the person who creates it is its owner.

A person can belong to several workspaces. After signing in they land in the earliest one they are an active member of; the workspace API switches between them (POST /api/v1/workspaces/switch).

How people become members​

There is no password sign-up and no "invite a colleague by email" screen. People join an organisation workspace through its identity systems:

RouteHowRole given
Workspace single sign-onThe workspace registers its own OpenID Connect or SAML provider. Anyone it signs in, with an address in a domain the workspace has verified, joins on first sign-in.The provider's configured role: creator by default; never owner or admin.
SCIM provisioningThe organisation's directory creates, updates and suspends members.A default role, or one mapped from directory groups; never owner or admin.
Integration launchAn instructor launched from a connected integrated platform.Presenter by default, as the integration is configured.

Who administers​

RoleCan
OwnerEverything, including single sign-on, SCIM, the audit log, API keys, webhooks, and deleting the workspace.
AdminEverything except those workspace-level controls: connected systems, data retention, workspace export, and all activity, session and results work.

See Members and roles for the full table.

Where administration happens​

The console's Settings page covers data retention, the workspace export, deleting the workspace and deleting your own account. The Integrations page covers API keys, webhooks and connected systems. Single sign-on, SAML, SCIM tokens and the audit log are configured and read through the workspace API, signed in as an owner; each page in this section names the calls.

Branding​

An owner sets the workspace's branding in Settings, Branding:

  • A logo. Pick or upload an image from the workspace's image library and say what it shows - usually the organisation's name, which screen readers read out. It must be an uploaded image (a PNG works; SVG is not accepted), not a link to another site, so no device in the room fetches it from a third party. The logo appears on a projector wall opened with a PIN and on participants' devices, before the session's title, in every session the workspace runs.
  • The projected wall's theme. An accent colour, used for every chart's bars, slices and highlights; a background, Night (the dark wall) or Brand (the accent over it, which needs an accent); and a typeface: System, Bricolage Grotesque, IBM Plex Sans or Serif.

Settings previews the theme on a small wall and warns before saving when the accent would be hard to see against the background, or the wall's white text hard to read. It is a warning, not a refusal. Participants' devices keep Pollinator's own colours, and a wall opened with Open wall from the signed-in run console does not show the branding yet.

Changes are recorded in the audit log as branding.changed. The same settings are available through the workspace API at GET and PUT /api/v1/workspaces/current/branding.