Organizations¶
Platform-admin only: onboard new client organizations, invite their first admin, and enter any client organization to help its owner.
Everything on this page requires the platform_admin role, a PulseTech-level role that sits above every individual organization. Ordinary org admins do not see any of it. Controls live under Platform → Organizations in the sidebar, alongside Signups.
What a client organization is¶
Each client is a fully isolated organization with its own members, courses, reports, and data. Creating one provisions its tenant and sets its edition so that everything is correct before its first admin ever signs in.
Creating a client organization¶
Most organizations are created by approving a request on the Signups page, which fills all of this in from what the applicant told you. Use New client when you are onboarding someone who never used the interest form: a client who came in through a conversation, or a demo organization.
Click New client and fill in:
| Field | Notes |
|---|---|
| Organization name | The client's display name |
| Alias | A stable slug, auto-filled from the name (editable) |
| Admin email | Who receives the first-admin invitation |
| Edition | Enterprise or Community; seeds the client's default feature set |
Click Create client. PulseLMS provisions the organization and invites the admin.
The invitation flow¶
What the admin email does depends on whether that person already has a PulseLMS account:
They are granted the org_admin role on the new organization immediately and can administer it on their next sign-in.
They receive an invitation email and become the organization's org admin the first time they sign in.
Either way, the new organization then runs itself, and its admin invites everyone else. Organization creation is recorded in the audit log.
The new organization is also seeded with the Active Shooter Response example course, so its Authoring Studio is not empty on the first sign-in. It arrives unlisted (staff can see it, members do not) and its new admin can assign it, list it in the catalog, or delete it. It is copied in the background and can take a minute or two to appear. See getting started.
Editing a client organization¶
Click Edit on any provisioned client to correct its name or change its edition. This is the fix for an organization that was provisioned under a placeholder: a name typed into the New client form, or whatever the applicant put in the interest form.
| Field | Notes |
|---|---|
| Organization name | Saved in PulseLMS and in SSO, so the admin console and invitation emails match what the customer calls themselves |
| Alias | The client's public catalog URL. Changing it does not break the old one; see below |
| Edition | Changes which features are on by default for this client |
Each change is recorded in your audit log.
Why the name can be in two places
A client's own admin can rename their organization under Settings, which changes the name in PulseLMS but deliberately not in SSO: the SSO organization is shared with every other PulseTech product, and one product's customer should not rename it for the others. When the two disagree, the Organizations list shows the PulseLMS name with SSO still says "…" underneath. Saving Edit sets both and the line goes away.
Changing an alias does not break the old link
The alias appears in the public catalog URL (?org=<alias>), and whoever saved that URL has no way of learning it changed. So every alias an organization has ever held goes on resolving, and the response reports the current one alongside the alias that was asked for. Old links keep working indefinitely; there is nothing to migrate.
A retired alias is also reserved permanently; no other client can be given it. That is not tidiness: if a freed alias were handed to someone else, every saved link would quietly start returning a different organization's catalog, with nothing anywhere reporting an error.
An organization can take back an alias it used before, so a mistyped rename is fixable. Aliases are lowercase letters, numbers and hyphens; a short list of names that would collide with a path (api, admin, verify, login, …) is refused.
One thing the rename does not change is the organization's alias in SSO, which is fixed at creation and cannot be edited; it is an internal key, and nothing customer-facing uses it.
Viewing a client as its owner¶
To support a client, a platform admin can enter their organization and see it exactly as its own org admin does: their courses, people, and reports.
- On the Organizations page, click View as owner on a provisioned client.
- Confirm the prompt.
You are now operating inside that organization.
The act-as banner and full audit trail
While you are viewing another organization, an amber banner is shown across the app with an Exit control to return to your own context. The switch into a client organization is recorded in your audit log; entering a client and acting on their behalf is fully attributable to you. Use it only to support the client, and exit when you are done.