Team and workspaces

Invite people, assign roles, and work across multiple workspaces.

Your work lives in a workspace: a single organization's collection of apps, content, domains, and settings. You can belong to more than one, and switch between them any time.

When you create one you pick its address, the name.tessryx.app subdomain it and its sites live at. Some names aren't available: very short ones, names already taken, and words held back to prevent impersonation (login, admin, a well-known brand, and the like) are refused with a "try another" message rather than a specific reason. Pick something short and specific to you.

#Inviting people

From Dashboard → Members (and Invites), send an invitation by email. When someone accepts, they join the workspace with the role you assign. Remove a member and their access ends immediately. Inviting and removing members is reserved to the workspace owner.

#Roles

Each member holds one role, which sets what they can do:

Roles are cumulative. Each can do everything the one below it can, plus more:

RoleCan
OwnerEverything an Admin can, plus manage team members, billing, and deleting the workspace
AdminEverything a Maintainer can, plus set secrets and custom domains
MaintainerBuild and publish everything: schemas, pages, workflows, integrations, schedules, apps
EditorEdit and publish content, upload media, and run workflows
ViewerRead everything in the workspace; change nothing

Give people the least role that lets them do their job: an editor who only touches copy doesn't need admin. Roles are also what team-only pages check, so the same role that lets someone edit in the web app can let them into an admin page on your site.

The Owner role is special: there's always exactly one, and it carries billing, member management, and the ability to delete the workspace. Ownership can be transferred but not simply assigned like the others.

#Switching workspaces

If you belong to several workspaces, switch between them from the account menu (top-right). Everything (apps, content, members, billing) is scoped to the workspace you're currently in, so double-check which one you're viewing before you publish or change settings.

#Workspaces and your connected agent

A connected agent is authorized against one workspace. To have it build in another, connect it again and choose that workspace during authorization.