Workspaces, projects and members

You will learn how Tixio organizes people and work through workspaces, projects, visibility, roles, members, invitations, and archived projects.

This page explains the access model. For step-by-step instructions, use Set up workspaces and projects and Manage members and access.

Workspace

A workspace is the top-level boundary for your organization or team. It contains projects, members, settings, integrations, saved views, dashboards, and workspace-level administration.

The workspace has:

A Name, which owners and admins can rename later.
A Short name, which is set when the workspace is created and used in URLs.
Members with workspace roles.
Settings such as Members, Integrations, Webhooks, Audit log, Data portability, AI assistant, Notifications, API keys, SSO, and archived projects where available. Personal API keys are managed under Settings > API keys; workspace service accounts are administered by owners and admins through the REST API (see Manage API keys and service accounts).

Workspace owners and admins use Settings > AI assistant to review token usage and set AI token limits. For details, read AI assistant and chat.

Most teams start with one workspace.

Workspace picker

After sign-in, the workspace picker shows the workspaces you can access and any pending invitations. It highlights the workspace you used last and includes an option to Open last workspace immediately (skip this screen).

Use the picker when you move between workspaces, accept invitations, or need to log out and use a different account.

Project

A project is where day-to-day issue work happens. Projects have their own issue key prefix, issue surfaces, backlog, cycles, versions, dashboards, automation, statuses, members, and settings.

Each project has:

A Name.
An optional Description.
A Short name, set at creation and used in URLs.
A Key, set at creation and used for issue keys such as PLAT-1.
Visibility, which controls who can access it.

Project visibility

Project visibility determines who can see the project:

Private: project members only.
Team: all workspace members.

Use private projects for sensitive work, customer-specific work, or limited collaboration. Use team-visible projects when everyone in the workspace should be able to find and contribute to the work.

Workspace owners and admins have administrative access across projects.

Workspace roles

Workspace roles control workspace-level administration.

Role	What it can do
Owner	Full workspace control. Owners can change member roles, manage settings and integrations, invite and remove members, and create or archive projects. Can create private and shared saved views.
Admin	Can manage workspace settings and integrations, invite and remove members, and create or archive projects. Admins cannot change other members' workspace roles. Can create private and shared saved views.
Member	Can access the workspace and collaborate on projects they can access. Members cannot invite workspace members or change workspace settings. Can create private and shared saved views.

Use Member for most people. Use Admin only for people who need to manage workspace operations. Keep Owner access rare.

Project roles

Project roles control access inside a project.

Role	What it can do
Admin	Can manage project members, settings, workflow, automation, and CSV imports. Workspace owners and admins have project-admin access automatically.
Member	Can create and edit issues, cycles, labels, comments, and attachments.
Viewer	Can read project issues and data, but cannot create or edit. Can open shared saved views and create private saved views; cannot create shared workspace views.
Guest	Read-only access for external collaborators invited only to this project. Can open shared saved views and create private saved views; cannot create shared workspace views.

For private projects, project roles are the main way to control access. For team-visible projects, workspace membership grants access, but explicit project roles are still useful for admins, viewers, and guests.

Invitations

Workspace invitations add people to the workspace. Project invitations add people to a project. If a project invite is sent to someone who is not yet a workspace member, Tixio can add them to the workspace automatically so the project invite works.

Pending invitations appear in member lists until accepted or cancelled. Invitees should use the same email address that received the invitation.

Archived projects

Archiving a project preserves issue data but hides the project from normal navigation and search. Workspace owners and admins can view archived projects from Settings > Archived projects and restore them when needed.

Use archive for projects that are no longer active but whose history should remain available. Do not archive a project just to hide unfinished work; use statuses, labels, saved views, or project visibility instead.

How the pieces fit together

Use this rule of thumb:

Workspace roles decide who can administer the workspace.
Project visibility decides the default audience for a project.
Project roles decide what a person can do inside a project.
Invitations are how people receive access.
Archived projects preserve old work without cluttering daily navigation.