Identity & Access
How people get onto the platform, what they can reach once there, and how they are removed. If you are setting up a new organization, work through Authentication first, then User lifecycle.
An identity is one email address with access to Rescale. A user is that identity's membership of a single workspace. One identity can be a user in several workspaces, which is why deactivating someone from one workspace doesn't necessarily remove them from the platform. See user lifecycle.
Authentication
How someone proves who they are. Most organizations settle this once: either you federate to your own identity provider with SSO, in which case your IdP owns passwords and second factors, or members sign in with a Rescale password, in which case the password policy and MFA pages below are what govern them.
User lifecycle
Getting people onto the platform and off it again. The order matters here: offboarding forces decisions about a departing user's jobs and files that cannot be undone, so it is worth reading before you need it rather than during.
Controls and visibility
Constraints on where access can come from, and the records of what was done. These are mostly organization-level and mostly set once, with the exception of access restrictions, which members can also apply to their own clusters.
Related
- Organizations & workspaces — the structure users belong to, and the billing boundary
- Budgets & deposits — per-member spend controls
- Sharing — granting access to individual jobs and files