Users And Groups

Kimura SCM access is managed through users and groups:

• A user is an account that can connect to a server (for example via Sso or Password).
• A group is a set of users used to grant access in bulk.

If something doesn’t look right in the UI (missing repos, missing actions), it’s often because of group membership or group access rules.

Users

Users are created and managed by administrators. A user typically has:

• a display name (Name) for UI/user-facing references,
• a login name (LoginName) used for authentication (often an email or OIDC identifier),
• an authentication type (for example Sso or Password),
• and membership in one or more groups.

Name and LoginName can be the same value, but they serve different roles:

• Name is how Kimura displays and manages the account in user/group operations.
• LoginName is the credential identifier used at login time.

Groups

Groups are how teams avoid setting permissions user-by-user. Instead, users are assigned to groups like:

• Developers
• Artists
• Build
• Admin

Admins then configure access rules for each group (repositories, folders, files).

How Groups Affect What You Can Do

Group membership influences which repositories/paths you can see and which actions are available (sync, edit, submit, lock, etc).

For more information, see the document on permissions and group access.

Users, Groups, And Remote Stashes

Remote stashes can be shared with specific users and/or groups (for example via “owners” and “viewers”), depending on what your server supports and how it’s configured.