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.”
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 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.