Decide who gets in, and what goes live.
The two controls a professional education programme is built on. Choose how people join, approve them by hand if you want to, put each hospital, dealer or region in its own organisation, and keep a review step between an author and the catalogue.
A 30-minute walkthrough shaped around your programme. No card, no commitment.
Four decisions, in order.
Each one is a setting your team changes, not a project.
Choose the sign-up rule
Closed (invite only), open, approved email domains, or approval required. Change it at any time in Settings; the domain list only applies under the approved-domains rule.
Place people in organisations
A hospital, trust, practice, dealer or region becomes an organisation with its own manager, and sites can sit under a parent. Managers see their own people and their records only.
Limit what each organisation sees
Make a course visible to chosen organisations, with a start and end date for each. Everyone else never sees it in the catalogue.
Review before publishing
Authors submit. A tenant admin includes or rejects each course with a note. Only included courses reach the catalogue, and scheduled dates take them down on time.
The four sign-up rules.
Set once in Settings, changed whenever you need to.
Organisations
Each organisation sees its own people and nothing else.
Hospitals, trusts, practices, dealers or regions become organisations, each with a manager who sees their people and their records. Sites can sit under a parent organisation. Courses can be visible to some organisations and not others, with dates, and an organisation can carry its own logo and colours where a customer wants its own look.
- Organisation managers see their own learners only
- Parent and child organisations for a trust with several hospitals
- Per-organisation course visibility with start and end dates
- Per-organisation branding on top of your platform defaults
Review
A review step between the author and the catalogue.
Give your content team author accounts. Authors build courses in the builder or upload SCORM, see and edit only their own courses, and submit each one for inclusion. A tenant admin includes or rejects it with a note the author sees.
Hotline keeps that one decision per course, with who made it. It does not hold a multi-stage sign-off record with reference codes and dates of preparation. If your code of practice needs one, keep it in your own system and record the outcome here.
- Authors see and edit their own courses only
- Include or reject, with a note
- Only included courses reach the catalogue
- Start and end dates take content down automatically
What Hotline does not do today
There is no "I am a healthcare professional" tick box in front of the content, and no lookup of the NMC, GMC or HCPC registers. The sign-up rule and the approval queue are the gate, and the check behind it is yours. If a logged self-declaration matters to your programme, say so on the walkthrough.
Access control that stands up to a security review.
The same controls your IT team will ask about, on one page with the hosting, the sub-processors and the encryption.
Security and data protection- Two-factor on every plan
- Single sign-on (SAML) and SCIM on the Provider Plus and Group plans
- An audit log across admin actions
- Each customer's data isolated
Access and approval questions
Yes. Under the approval-required rule, anyone can apply and nobody gets in until a member of your team approves them. The queue shows who applied and when, the account becomes active when you approve it, and the approver and the time are recorded on the account.
Yes. Under the approved-domains rule, registration is limited to the email domains you list. Anyone with another address is turned away at the form. You can also block disposable email addresses under any rule.
Yes. Each hospital, trust or practice is an organisation, and a course can be made visible to chosen organisations with a start and end date for each. People outside those organisations never see it in the catalogue.
Tenant admins publish their own courses directly. Authors cannot: they submit, and a tenant admin includes or rejects each course with a note. Only included courses reach the catalogue.
No. If the workspace requires approval, or your single sign-on connection is set to require it, a person signing in for the first time through SSO lands in the queue like everyone else.
Yes. Every course can have a start date and an end date, and a course made visible to an organisation can have its own dates for that organisation. Outside those dates it leaves the catalogue on its own.
See your access rules on Hotline.
Tell us who should get in and who should sign off. We will set both up on a demo academy on the call.