> For the complete documentation index, see [llms.txt](https://docs.infraglide.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infraglide.com/settings-governance-and-rbac/organization-settings.md).

# Organization & Workspace Administration

InfraGlide tenancy is nested: **Organization → Workspace → Sandbox**. This page covers what admins configure at each level.

***

### Terminology Reminder

| UI label     | API / storage name                                               |
| ------------ | ---------------------------------------------------------------- |
| Organization | `organizations` (from signed-in identity — no header org picker) |
| Workspace    | `folder` / `selectedFolderId`                                    |
| Sandbox      | `project` / `selectedProjectId`                                  |

The header shows the active pair as **`Workspace / Sandbox`**.

***

### Organization Setup

Org Admins open **Settings → Organization setup** (or `/onboarding`) to run the wizard:

1. Welcome
2. Workspaces
3. Sandboxes
4. Credentials
5. Cloud APIs
6. Storage
7. Git
8. Finish

#### Org-level settings (examples)

* **Cloud provider policy** — allow/block AWS, GCP, Azure for the whole org (Settings → Cloud).
* **Notification integrations** — Slack / Teams / Google Chat webhooks (encrypted at rest).
* **Seat license requests** — when enabled for your deployment.
* GCP API profile overrides and related org JSON fields for advanced tenants.

***

### Workspaces

Workspaces are top-level team or business-unit areas.

* Create/manage via onboarding or folder APIs / admin UI flows.
* Org Admins typically see all Workspaces; other users only see Workspaces they are granted.
* If a user has no accessible Workspaces, **FolderAccessGuard** sends them to `/no-access`.

***

### Sandboxes

Sandboxes are deployable environments inside a Workspace (`dev`, `staging`, `prod`, …).

* May set `environmentTier` for promotion-style naming.
* **Every pipeline and credential requires a Sandbox.**
* Switching Sandboxes in the header filters My Pipelines, Credentials, dashboard metrics, and related lists.

***

### Who Can Administer What

| Role signal         | Typical powers                                                     |
| ------------------- | ------------------------------------------------------------------ |
| **Org Admin**       | Org settings, onboarding, all Workspaces, invitations at org scope |
| **Workspace Admin** | Admin grant scoped to a Workspace (`access_level` 2)               |
| **Sandbox Admin**   | Admin grant scoped to a Sandbox (`access_level` 3)                 |
| **Editor / Viewer** | Pipeline/module permissions without full admin                     |

Exact enforcement uses RBAC grants — see [Role-Based Access Control (RBAC)](/settings-governance-and-rbac/rbac.md).

***

### Preferences vs Org Admin

All users can edit personal preference tabs in Settings (profile, appearance, defaults, notifications preferences, Jane preferences, feature requests). Org-wide cloud policy and onboarding remain Org Admin controls.

***

### See also

* [User Management & Invitations](/settings-governance-and-rbac/user-management.md)
* [Role-Based Access Control (RBAC)](/settings-governance-and-rbac/rbac.md)
* [Core Concepts & Terminology](/getting-started/core-concepts.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.infraglide.com/settings-governance-and-rbac/organization-settings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.