> 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

Everyone who uses CloudRaker in your organization is a **member**. You manage members — invite them, assign their roles, and remove them — on the **Users** page under the **Admin** group. This page also explains how organization-level roles relate to the separate, per-space access model.

**Users** is admin-only, like the rest of the **Admin** group. If you don't see it in the sidebar, you don't 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."*

<img src="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%2F20260726%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260726T051448Z&X-Amz-Expires=604800&X-Amz-Signature=869ef5ce33d98c866016285c36dd26416cdeffe4cac5a617a85ac39f1216ef97&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject" alt="Admin Users page: search field, role filter, Invite user button, and a table of members with User, Roles, and Last active columns" />

There is no separate **Roles** page. Role assignment happens right here 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. In the app shell, it's what controls whether you see the **Build** and **Admin** groups in the sidebar — only admins do. Behind the scenes, the gateway is the real authorization boundary: it checks your role and permissions on every request, so hiding a menu is a convenience, not the security.

### Per-space access

Access to an individual space is set **separately**, on that space's **Settings** tab — not on the **Users** page. Space roles are cumulative: **Viewer**, **Contributor**, **Manager**, and **Archiver**. Being an org member doesn't automatically give you access to every space; a space grants its own roles. See [Spaces overview](/spaces/overview) for how space membership works.

Rule of thumb: use **Users** to control who's in the organization and whether they're an admin; use a space's **Settings** tab to control who can do what inside that space.

## Where to go next

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

How spaces work and how per-space roles are assigned.

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

Set your organization's logo and switch between organizations.