Administer an organization

Create the organization

Only platform administrators (addresses listed in the server configuration) can create an organization. The creator becomes its admin and can then invite and delegate.

Members and invitations

• Invite people: paste addresses, one per line or separated by commas, or import a CSV email,role. Choose a role (admin, editor, member) and, if needed, the groups to join.
• Each person receives an email; they accept or decline the invitation after signing in. Pending invitations can be revoked.
• Role changes and removals can be applied to several members at once.
• The last admin of an organization cannot be removed or demoted.

Role	Can
admin	Everything: members, groups, settings, activity log, themes
editor	Create, edit, publish, withdraw and delete themes
member	Use the published themes in VS Code

Single sign-on (SSO OIDC)

An organization can have its members sign in through its identity provider (OIDC). The provider is registered by a platform administrator, for a domain, after checking that the organization owns that domain. People whose email belongs to the domain then sign in through the provider and join the organization as member.

Groups

Groups are used to restrict access to certain versions: for example, a theme reserved for a team or a client.

• Create a group, add members to it (several at once) or remove them.
• A version is targeted at the whole organization or at a group. admin and editor users see all versions.
• A group used by a theme version cannot be deleted.

Publish a theme

1. New theme: import a .css or paste the CSS. Its @theme name becomes the theme's name, permanently.
2. The validator runs while you type; fix until there are zero errors. The preview shows the control slides rendered with the theme. The detailed rules are in The theme validator.
3. Save draft with its number (1.2.3) and its release notes. A draft may keep contract errors, but not parsing, identity or security errors.
4. Publish, choosing the Audience: the whole organization or a group. The server revalidates; the version becomes immutable.

A New version starts from the CSS of the latest one: same @theme name, number higher than the latest published version.

AI assistant

If the organization has enabled it (Organization settings, disabled by default, and only if the portal is configured for it), the editor proposes a fix for each error and a side chat. Proposals are revalidated and never applied without approval. Embedded resources (base64 images, fonts) are replaced with placeholders before being sent to Claude.

Withdraw, delete, roll back

• Withdrawing a published version stops its distribution. Copies already installed remain usable; VS Code offers the latest published version.
• Deleting a theme stops all its versions. You can designate a Replacement theme, which VS Code will offer to the people concerned.
• To roll back, publish a new version from the old CSS.

Theme storage

By default, published CSS files are in the platform storage (Cloudflare R2). An organization can choose its own storage:

• S3-compatible: AWS S3, Cloudflare R2, Google Cloud Storage (interoperability), Scaleway, OVHcloud, MinIO…;
• Azure Blob Storage, via SAS URL.

A button tests the connection (writing, reading, then deleting a file). The choice applies to new publications; existing versions stay where they are. Credentials are encrypted server-side and never shown again.

VS Code sessions

Each person sees their VS Code connections in Account settings and can revoke them. A connection lasts 30 days; a web session, 7 days. Log out can also revoke all VS Code connections.

History

Invitations, access changes, theme operations, storage, SSO and assistant are logged in the Activity section.