# Organizations and workspaces Manage your Tracix organization and its workspaces in the console, decide who can open each workspace, update releases, and suspend or delete workspaces. Your organization holds your people, sign-in rules and billing; your workspaces hold your data. This page covers managing both in the console. To create a workspace, see [Create a workspace](https://tracix.io/docs/get-started/create-a-workspace). ## Your organization You create the organization when you sign up, and you become its Owner. You name it during sign-up; to rename it later, open **Organizations**, open the menu on your organization's card and choose **Rename**. The card also shows how many workspaces and members the organization has, and its plan. Each user account belongs to one organization. Accepting an invite to another organization moves your account there and removes your access to the old organization's workspaces. If you're the Owner of an organization, you can't accept an invite to another one. Deleting an organization isn't available in the console yet. To close an organization, [contact support](https://tracix.io/contact). ## Who can manage workspaces Managing workspaces in the console needs the Owner, Admin or MSP admin role: creating them, controlling access, changing release settings, suspending, resuming and deleting. Using a workspace is separate: anyone, organization Admins included, needs to be added on its **Access** tab to open it. See [Users and roles](https://tracix.io/docs/admin/users-and-roles). ## The workspace page Open **Workspaces** and select a workspace to see its page. The header shows the status, the workspace's address and its region. The tabs: | Tab | What it's for | | ----------------- | ------------------------------------------------------------------------------------------------------------------------------ | | **Overview** | Progress while the workspace is being provisioned, resumed or deleted, the **Workspace info** card, and **Open in app.tracix** | | **Configuration** | Renaming, endpoints, the backend connection, release updates and the sandboxed MCP runner | | **Access** | Who can open the workspace and with which role, and the source IP allowlist | | **Logs** | A live tail of the workspace's own logs, once it's active | | **Danger zone** | Suspend, resume and delete | For the addresses that SDKs and collectors use, copy them from inside the workspace: **Applications › APM & Traces › Setup** lists the OTLP endpoints, and the collector install flow fills in the rest. See [Endpoints and ports](https://tracix.io/docs/reference/endpoints-and-ports). ## Rename a workspace On the **Configuration** tab, change the **Display name** under **General** and select **Save name**. Renaming changes the display name only: the workspace's address keeps the name it had when you created it, so links and collectors keep working. ## Control who can open a workspace The **Access** tab lists everyone who can open the workspace, with their workspace role. * To add someone, select **Add member**, pick a member of your organization, choose **Admin**, **Editor** or **Viewer**, and select **Grant access**. To add someone who isn't in your organization yet, [invite them](https://tracix.io/docs/get-started/invite-your-team) first. * To change someone's role, choose a new role from the menu on their row. * To take away their access, select the remove icon on their row and confirm **Revoke**. They lose access to this workspace immediately and keep their organization membership. The person who created the workspace starts as its Admin. ### Restrict source networks The **Source IP allowlist** on the same tab limits which networks can reach the workspace's public endpoints. While the list is empty, traffic from the internet is allowed; add CIDRs, such as `10.0.0.0/8` or `203.0.113.5/32`, to allow only those networks. Authentication still applies where an endpoint requires it. Enter a CIDR and an optional description and select **Allow**. Changes take effect when the workspace's next reconciliation succeeds, and the console says so when you make them. Removing the last entry allows internet traffic again. ## Release updates The **Updates** card on the **Configuration** tab controls which Tracix release the workspace runs: | Field | What it means | | ------------------- | ---------------------------------------------------------------------------------------------------------------- | | **Channel** | The release channel the workspace follows: `stable` by default | | **Auto-update** | **On** moves the workspace to each new release on its channel. **Off** keeps it where it is until you update it. | | **Current release** | The release the workspace runs | | **Available** | **Update to** a newer release on your channel, when there is one | Selecting **Update to** pins the workspace to that release and queues the update. Changing these settings needs the Owner, Admin or MSP admin role. ## Suspend, resume and delete | Action | Available when | What happens | | ----------- | -------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Suspend** | The workspace is `active` | Stops the workspace's services and keeps its data. Runs right away, with no confirmation. | | **Resume** | The workspace is `suspended` | Restarts the services. The status passes through `provisioning` back to `active`. | | **Delete** | The workspace is `active`, `suspended` or `failed` | Permanently destroys the workspace, its ClickHouse database, ingest keys, allowlist entries and custom domains. Objects in the workspace's storage bucket expire 30 days after deletion. | **Suspend** and **Resume** are in the header and on the **Danger zone** tab. **Delete** asks you to confirm in **Delete this workspace?**; it can't be undone. The status changes to `deleting` while Tracix tears the workspace down, then `deleted`. If a deletion stops partway, select **Retry deletion**. Only one operation runs on a workspace at a time. If you start another while one is running, the console reports `A provisioning operation is already in progress`; wait for the first to finish. ## Next steps - [Users and roles](https://tracix.io/docs/admin/users-and-roles): What each organization and workspace role can do - [Invite your team](https://tracix.io/docs/get-started/invite-your-team): Bring people in and give them workspace access - [Billing and usage](https://tracix.io/docs/admin/billing): Plan, usage meters and invoices