Members and roles

Invite people and assign roles. Learn how org roles relate to space access.
View as Markdown

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

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