> ## Documentation Index
> Fetch the complete documentation index at: https://docs.acrity.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Workspace settings

> Review and configure workspace settings in the Acrity Console.

Workspaces organize people, repositories, policies, credentials, billing, and audit. Each workspace represents an organization, unit, customer, or separate administrative environment.

## Who can access

* **Workspace admin** administers all workspace settings, including admin-gated areas. Platform admins also have access.
* **Billing Manager** manages areas related to workspace billing.
* **Maintainer** and **Member** can view the areas their role allows.

Roles are fixed capability sets defined by Acrity. They are not configurable per organization.

## When to use

Use workspace settings to:

* review basic workspace data;
* adjust default language;
* configure allowed signup domains;
* transfer ownership;
* view onboarding state and pending items;
* access workspace administrative areas.

## Main settings

You can edit the workspace Name and Description, plus Allowed domains and the Language picker. The Slug is a read-only identifier: you can copy it, but you cannot change it here.

| Field           | Purpose                                                                                         | Recommendation                                                              |
| --------------- | ----------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
| Name            | Name displayed in the Console and administrative areas.                                         | Use the public name of the organization or area.                            |
| Slug            | Read-only, permanent identifier assigned when the workspace is created.                         | Copy it when you need to reference the workspace; it cannot be edited here. |
| Description     | Workspace context for workspace admins.                                                         | Explain the workspace area or purpose.                                      |
| Allowed domains | Email domains authorized for association or signup when enabled.                                | Include only domains controlled by the organization.                        |
| Language        | Default language used by the workspace experience and review outputs when there is no override. | Choose the language expected by teams receiving comments.                   |

## Workspace language

Workspace language defines the default preference for communications and review outputs. A repository can have its own language when a team needs to receive reviews in another language.

To configure:

1. Select the correct workspace.
2. Open workspace settings.
3. Find the language setting.
4. Select the desired language.
5. Save changes.

## Transfer ownership

Transferring ownership changes the main owner of the workspace.

Before transferring:

* confirm that the new owner already has appropriate access;
* review billing and pending invoices;
* notify affected workspace admins;
* keep at least one active workspace admin in the workspace.

<Warning>
  Do not transfer ownership to a personal or temporary account. Use an account administered by the organization.
</Warning>

## Allowed domains

Allowed domains help control which emails can associate with the workspace in flows that use a corporate domain.

Best practices:

* use only organization domains;
* remove old domains after migrations;
* do not include public domains such as free email providers;
* combine this setting with periodic member review.

## Initial workspace checklist

* Workspace created with clear name and description.
* Default language defined.
* Workspace admins invited.
* Billing or trial configured.
* Connected Apps installed or credentials registered.
* Repositories connected.
* Default review policy reviewed in the Policy Engine.
* API Keys and webhooks created only when there is an external integration.

## Common issues

| Symptom                         | What to check                                                                                                         |
| ------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| I do not see workspace settings | Your role might not have access. Use the workspace selector or ask a workspace admin for access.                      |
| I cannot save changes           | Check required fields, permissions, and screen validation messages.                                                   |
| Review language did not change  | Check whether the repository has its own configured language. Repository language can override the workspace default. |
| A user cannot access            | Confirm invite, assigned role, and allowed email domain.                                                              |

## Next steps

After configuring the workspace, continue with:

* [Members and users](/en/console/members-and-users) to add people;
* [Connected Apps](/en/console/connected-apps) to install providers;
* [Repositories](/en/console/repositories) to connect projects;
* [Policy Engine](/en/console/policy-engine) to review the default policy.