Organization administration

Manage members, groups, content sharing and privacy from Admin.

Organization admins use Admin in the sidebar to manage members and settings. Course editing permissions and licenses are separate from the organization admin role.

The menu names below follow the English interface. Some settings are managed by SceneSnap and appear read only; contact SceneSnap to change them.

Add members

Open Admin → People.
Enter an email in Add by email, choose the member or admin role, then choose Add.
If the person has not registered yet, the row shows Pending sign-in. Access activates when they sign in with that address and the sign-in confirms they own it: Google, a Microsoft work or school account, or your SSO. A personal Microsoft account (Outlook, Hotmail) does not confirm the address, so the row stays pending. The same applies to someone who already has an account whose address was never confirmed: they join at their next confirming sign-in.
To withdraw an invitation nobody has used yet, choose Revoke invitation on its row. Someone who has already joined is deactivated instead.

A person has one membership per organization. If you invite an address of someone who is already a member under another address, their next confirming sign-in folds the invitation into the membership they have: they keep a single row, with the groups of both and the admin role if either had it. Once someone has joined, Admin → People shows the address of their SceneSnap account; while an invitation is pending, and for members managed by SCIM, it shows the address your organization provided.

For several people, choose Import CSV. Supply an email column and an optional role column containing member or admin. You can upload a file or paste a list. Each import accepts up to 1,000 rows; review skipped and invalid rows before importing, then review the result and download the error report if needed.

Someone who belongs to several organizations works in one at a time and picks it at the top of the sidebar. Admin, branding, the organization that owns new content and the lists (Start, Learn, courses, files, Arola) follow the selected one; joining another organization does not change it. Personal content, and content shared by organizations you are not a member of, show whichever one is selected. A link to another of your organizations' content still opens.

Membership does not automatically share every course. Share a course with the organization, a group or the person to make it available.

Groups

Use Admin → Groups to create groups and manage their members. In Admin → People, select members to add them to or remove them from a group. Share a course with a group to give its members access.

Groups synchronized by SCIM are read only in SceneSnap. Change them in your identity provider. Deleting a group removes shares made through it without deleting its people from the organization.

Admin → Settings → Content sharing shows who the organization's content can reach and who it belongs to. SceneSnap sets both choices as agreed with your organization; to change them, contact SceneSnap at support@scenesnap.co.

Choice	Effect
Members only	Organization content stays within the organization. Outside sharing, public links and web publication are restricted.
Anyone	Editors may share outside the organization or publish where supported. Content still needs an explicit share or publication.
The organization	Organization admins can manage the content, and it stays with the organization when its creator leaves.
Whoever creates it	The creator keeps ownership and takes their content when they leave. It follows organization sharing rules while it belongs to the organization.

Switching to Members only revokes existing outside access, closes public links and withdraws published sites covered by the policy. Changing ownership does not move back content that a former member already took with them.

Learner privacy

Use Admin → Settings → Learner analytics privacy to choose Individual analytics or Aggregate only. Final-quiz outcomes can still be shown per learner in aggregate mode. See Data and privacy.

Inactive members

In Admin → Settings → Inactive members, turn on Deactivate inactive members and choose Days of inactivity, with a minimum of 30 days.

Counting starts from the latest activity, joining date or policy activation, whichever is most recent. A daily check applies deactivation after the threshold.
SCIM-managed members and accounts with only LTI or SCORM access are excluded. The last active administrator is protected.
Reducing an active threshold can deactivate members at the next check; the UI asks you to confirm it.
Turning the policy off does not reactivate members already deactivated. An admin must restore their access.
Deactivation keeps their account and data. It releases an assigned license, which an admin must assign again after reactivation.

For a member marked Managed by SCIM, change activation in the identity provider.

Appearance and notifications

Admin → Settings → Branding changes your organization's logo and app colors.
Admin → Settings → Feature visibility chooses which controls appear for admins and members. Hiding a control does not revoke access through a direct link. Use content permissions and sharing settings to control access.
Admin → Settings → Notifications allows or blocks categories of email for your organization. Blocking a category stops it even for members who enabled it personally. Allowing it still respects each member's preferences. Enabling learning emails can start delivery to existing members; review the confirmation before applying it.

Task	Where to go
Assign or remove a license	Admin → People; see Licenses.
Change automatic license assignment	Admin → Settings → Licenses
Choose how SCORM courses open	Admin → Settings → Opening SCORM packages; see SCORM.
Create or revoke a provisioning key	Admin → Settings → User sync (SCIM); see SCIM.

Admin pages exchange member email addresses, roles, activation status, group membership and license assignments with SceneSnap. Dashboards also request the learning information their privacy policy permits. They do not configure the identity provider or LMS for you; follow the integration's setup guide for those systems.