> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.cloudraker.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.cloudraker.com/_mcp/server.

# Members and roles

Each person who uses CloudRaker in your organization is a **member**. Manage members on the **Users** page under the **Admin** group. There you invite members, assign their roles, and remove them. This page also explains how organization roles relate to the separate per-space access model.

**Users** is admin-only, like the rest of the **Admin** group. If you do not see it in the sidebar, you do not have the **admin** role. Ask an admin.

## Manage members on the Users page

Open **Admin → Users** in the sidebar. The page description reads *"Invite people, manage their roles, and remove members of your organization."*

![Admin Users page: search field, role filter, Invite user button, and a table of members with User, Roles, and Last active columns](https://fdr-prod-docs-files-public.s3.us-east-1.amazonaws.com/cloudraker.docs.buildwithfern.com/93b96cb8d5fb1672c877d5d6024f4919fbd2e8d4a24a2fc87529cd83eaa763a9/docs/assets/images/guide/admin/users-table.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA6KXJSKKNFOCF7G4B%2F20260920%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260920T234527Z&X-Amz-Expires=604800&X-Amz-Signature=60145decb97b50f2172029491903768b18dc6630bc7255434c3cc102a2d1aafa&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)

There is no separate **Roles** page. You assign roles in the **Users** widget.

## Organization roles vs. space access

CloudRaker has two layers of access.

### Organization roles

Your **organization role** (for example, **admin** or **member**) decides what you can do across the whole organization. It controls whether you see the **Build** and **Admin** groups in the sidebar. Only admins see them. The gateway is the real authorization boundary. It checks your role and permissions on every request. A hidden menu is a convenience, not the security.

### Per-space access

Set access to an individual space **separately**, on that space's **Settings** tab, not on the **Users** page. Space roles are cumulative: **Viewer**, **Contributor**, **Manager**, and **Archiver**. Org membership does not give access to every space. A space grants its own roles. See [Spaces overview](/workspace/spaces/overview) for how space membership works.

Use **Users** to control who is in the organization and who is an admin. Use a space's **Settings** tab to control what each person can do inside that space.

## Where to go next

#### [Spaces overview](/spaces/overview)

Learn how spaces work and how you assign per-space roles.

#### [Organization settings](/admin/organization-settings)

Set your organization's logo and switch between organizations.