Platform Admin Guide
This guide explains how to use the Platform Admin portal: the area of PRIAM where the product team manages content shared by every customer organization, such as master policy templates, the risk-assessment question library and the HIPAA assessment.
Audience: Application Administrators, the people on the PRIAM team who sign in to
/platform-admin. You don't need to know how the app is built.Technical details live elsewhere: - API endpoints: API_REFERENCE.md - who can access what, and how it's enforced: RBAC_Matrix.md - operator and developer procedures (granting access, seeding scripts, data locations): the parking lot
What the Platform Admin portal is
The portal is separate from the customer side of PRIAM: - Owners have no access: an owner or administrator of a customer organization can't open it. - You don't see customer data: as a platform admin you have no special access inside any customer organization, and nothing in the portal shows or changes a specific customer's policies, people or incidents.
| What you can do | Customer owner / admin | Platform admin |
|---|---|---|
| Manage their own organization's policies | ✓ | — |
| Approve or reject their organization's policies | ✓ | — |
| Write master policy templates for every customer | — | ✓ |
| Publish template versions and notify customers | — | ✓ |
| Set rules that recommend templates by industry, state and business profile | — | ✓ |
| Maintain the risk-assessment questions, recommendations and industry weights | — | ✓ |
| Manage HIPAA assessment companies and participants | — | ✓ (HIPAA Admin) |
Signing in and finding your way around
- Go to
/platform-admin/loginand sign in with the email and password of your admin account. - You land on the hub. It's organized in tabs by function: Policy Admin, Risk Admin, HIPAA Admin, Tenant Admin, Reports and Resources. You only see the tabs and cards your account has access to, and the sidebar uses the same groups.
- No access? You'll see "This account does not have admin portal access." Ask the person who manages admin accounts to grant it.
There are two kinds of admin access, and an account can have both:
| Access | What it opens |
|---|---|
| Platform Admin | Policy Admin (Policy Templates, Template Rules, Import Catalog), Risk Admin (Risk Questions, Question Set Versions), Tenant Admin, Risk Content Health |
| HIPAA Admin | HIPAA Admin (Dashboard, Companies, Participants) and HIPAA Reports |
Sign out with the button at the bottom of the sidebar.
Getting or removing access is done by a developer with a script; there's no screen for it. Changes apply on your next page load. After HIPAA Admin access is granted, sign out and in again. (How: parking lot › Granting admin access.)
Policy Admin
Policy Templates
What they are
Master templates are the product team's standard policies. Each one defines the structure of a type of policy, such as a Data Retention Policy or an Acceptable Use Policy: its sections, and which sections are required or optional.
Customers don't write policies from scratch. When a manager in a customer organization starts a new policy, PRIAM suggests the most relevant templates (see Template Rules). The manager creates the policy from a template, which copies its sections in as a starting point. The policy keeps a link to the template and its version, so the customer can be told when the template changes.
When to create a template
- Coverage: a new regulation, industry standard or best-practice policy should be covered for customers.
- Baselines: a legal or compliance change needs a new standard baseline, e.g. a change in a state's privacy law.
- Common gaps: many customers write their own policy on the same topic and would benefit from a standard one.
Don't create a template for something specific to one customer, such as their own workflows or internal procedures. A template is the minimum or recommended standard; customers adapt it after adopting it.
Create a template
- Open Policy Templates and click New Template.
- Enter a Title (what customers see, e.g. "Remote Work Security Policy") and a Category (groups templates for customers, e.g. "Data Privacy", "Physical Security", "HR").
- Click Create to open the editor.
- Add sections with Add Section. Each section has:
- Title: the heading, e.g. "Scope", "Acceptable Use", "Enforcement".
- Body: the text. Where a customer's own details belong, type a placeholder:
{{COMPANY_NAME}},{{EFFECTIVE_DATE}}or{{JURISDICTION}}. - Optional: an optional section can be left out when a customer adopts the template. Required sections are always included.
- Drag sections into the order you want.
- Save at any time. The template stays a draft, invisible to customers, until you publish it.
Writing tip: address the customer's employees directly ("You are responsible for…"), and use
{{COMPANY_NAME}}instead of naming a company.
Publish a template
Publishing makes the template available to customers and their recommendations. It also tells every customer using an older version that an update is available. 1. Open the template and review every section. 2. Click Publish New Version. 3. Write changelog notes. Customer owners and admins read these in the update notice, so be specific: "Added a section on multi-factor authentication requirements following NIST SP 800-63B." 4. Confirm. PRIAM: - raises the version number and records your notes; - marks the template published; - finds customer policies based on an older version of it; - sends an update notice to those customers' owners and admins, in the app and by email.
Only policies that are published, expiring or approved get the notice; drafts and archived policies don't. Each customer then chooses to accept the update (bringing in the new sections) or dismiss it, from the policy's page.
A message confirms the result, e.g. "Template v4 published. 12 tenant policies notified."
Archive a template
Archive a template that's been replaced or no longer applies, e.g. the regulation was repealed. - Open the template and choose Archive. - Effect: customers can no longer adopt it, and it stops appearing in recommendations. - Existing policies: customers who already used it keep their policies unchanged, but get no more update notices.
Template statuses
| Status | Meaning |
|---|---|
| Draft | Being written. Customers can't see it. |
| Published | Live. Recommended to customers, and updates are announced. |
| Archived | Retired. Not recommended any more; existing customer policies are unaffected. |
Example: Remote Work Security Policy
A complete template you can create as-is.
Title: Remote Work Security Policy · Category: IT Security
| # | Section | Required | Text |
|---|---|---|---|
| 1 | Purpose | Yes | This policy establishes the security requirements that all employees of {{COMPANY_NAME}} must follow when working remotely. It is effective as of {{EFFECTIVE_DATE}}. |
| 2 | Scope | Yes | This policy applies to all employees, contractors, and third-party personnel of {{COMPANY_NAME}} who access company systems, data, or networks from any location outside a company-operated office. |
| 3 | Approved Devices | Yes | Only devices approved by {{COMPANY_NAME}}'s IT department may be used to access company systems remotely. Personal devices must be enrolled in the company's mobile device management (MDM) solution before use. All approved devices must have up-to-date operating system and security patches, approved endpoint protection installed and active, full-disk encryption enabled, and a screen lock that activates after no more than 5 minutes of inactivity. |
| 4 | Network Security | Yes | Employees must use the company-provided VPN when accessing internal systems. Use of public or unsecured Wi-Fi networks without VPN is prohibited. Home networks used for remote work must be secured with WPA2 or WPA3 encryption. Default router credentials must be changed. |
| 5 | Data Handling | Yes | Company data must not be stored on personal devices or unapproved cloud storage services. All work files must be saved to {{COMPANY_NAME}}-approved storage locations. Sensitive or confidential documents must not be printed in unsecured home environments unless expressly authorised by a manager. |
| 6 | Reporting Security Incidents | Yes | Any suspected security incident — including lost or stolen devices, unauthorised access attempts, or phishing emails — must be reported to the IT Security team immediately via the incident reporting system or by email to the security contact on file. |
| 7 | Acceptable Use During Remote Work | Optional | Company systems and internet access must be used primarily for business purposes. Employees should ensure that family members or other household occupants cannot observe or access company screens, documents, or data. |
Changelog notes for the first publish: Initial release of the Remote Work Security Policy template. Covers device approval, network security, data handling, and incident reporting obligations for remote employees.
The pre-built template library (12 templates and their rules) is maintained by developers. (Parking lot › Canonical template catalog.)
Template Rules
What they are
Template rules decide which templates PRIAM recommends to each customer. When a manager starts a new policy, PRIAM checks every active rule against the customer's profile (industry, state and business flags). It then lists the matching templates, highest weight first, each with the reason you wrote. Templates marked required by law show a red Required badge.
Without rules, customers see every template unsorted. With them, a healthcare company in California sees its privacy templates first, and a logistics company sees vehicle and driver policies.
When to create a rule
- Required: a template is legally required for an industry, state or kind of operation.
- Recommended: a template is highly relevant but not required, e.g. Remote Work Security for any company with remote workers.
- Prominent: a template should stand out even when many others match (give it a high weight).
A template can have several rules, e.g. one per industry and one per state. If any matching rule says "required", the template shows as required.
Rule fields
| Field | What it does |
|---|---|
| Template | The template this rule recommends. Only published templates are listed. |
| Industry (NAICS) | An industry code. A shorter code covers every industry that starts with it: 62 (Health Care) matches 6241 and 6243. Leave blank for any industry. |
| Jurisdiction | A US state, e.g. US-CA. Leave blank for any state. |
| Business flags | Profile flags such as remote_workers, processes_pii or fleet_vehicles. The customer must have all the flags you pick. Leave empty for any customer. |
| Weight | Higher appears first. Default 10. Use 50–100 for legally required templates, 10–30 for recommended ones. |
| Required by law | Shows the red Required badge. |
| Active | Turn a rule off temporarily, e.g. while its template is being revised, without deleting it. |
| Reason | Shown to the customer's manager to explain the recommendation. |
How matching works
A rule matches a customer when all three hold: - the industry is blank, or the customer's industry code starts with it; - the state is blank, or equals the customer's state; - the customer has every business flag the rule lists.
If several rules match the same template, the highest weight wins, and the template is required if any matching rule says so.
Create a rule
- Open Template Rules and click New Rule.
- Pick the Template.
- Fill in the matching fields. Leave a field blank to apply the rule more broadly.
- Set the Weight.
- Tick Required by law if the template is legally required for these customers.
- Write a Reason, e.g. "California law requires all employers to maintain a written data privacy policy (CCPA §1798.100)."
- Save. The rule takes effect for customers right away; no release is needed.
Try a rule before it goes live
There's no preview screen yet. To check a rule: 1. Create it with Active off. 2. Ask a developer to check what a test customer with a matching profile is recommended (API reference › GET /api/policies/recommend). 3. Turn Active on when it looks right.
Example: two rules for the Remote Work Security Policy
Rule 1: recommended for any company with remote employees
| Field | Value |
|---|---|
| Template | Remote Work Security Policy |
| Industry | (blank: any) |
| Jurisdiction | (blank: any) |
| Business flags | remote_workers |
| Weight | 30 |
| Required by law | No |
| Reason | Companies with remote employees should maintain a formal remote work security policy covering device standards, network security, and data handling expectations. |
Rule 2: required for California professional-services firms handling personal data
| Field | Value |
|---|---|
| Template | Remote Work Security Policy |
| Industry | 54 (Professional, Scientific, and Technical Services) |
| Jurisdiction | US-CA |
| Business flags | processes_pii, remote_workers |
| Weight | 70 |
| Required by law | Yes |
| Reason | California employers in professional services who process personal information and operate distributed teams must maintain documented security practices governing remote access. This satisfies obligations under CCPA (Cal. Civ. Code §1798.81.5) and California's Information Security Practices Act. |
What customers see:
- California professional-services firm (code 54xx, processes_pii and remote_workers):
both rules match. The template appears once, at the top, with weight 70 and a red Required
badge.
- Texas hotel (code 72) with only remote_workers: Rule 1 matches. The template appears as
Recommended, weight 30.
Import Catalog
The hub numbers the Policy Admin areas in the order you'd use them when setting up a new environment: 1. Import Catalog; 2. Template Rules; 3. Policy Templates.
Import Catalog brings PRIAM's built-in templates into your policy library: 1. Browse the catalog. 2. Tick the templates you want. 3. Click Import n Templates.
The results show what was imported; Import More starts again.
Risk Admin
Risk Question Library
Risk Questions is where you maintain everything behind the customer's risk assessment: - the questions customers answer; - the recommendations they get for weak answers; - the industry weights that decide how much each risk category counts for an industry.
The page has five tabs:
| Tab | Use it to | When changes reach customers |
|---|---|---|
| Content Health | Check that every industry has questions in every category, and spot problems | Read-only |
| Questions | Add, edit and retire questions | After you publish with Seed Control |
| Recommendations | Edit the recommended actions for each industry | Immediately |
| Industry Weights | Set how much each risk category counts for each industry | Immediately, for assessments completed from then on |
| Seed Control | Check the question library and publish it as a new question-set version | When you publish |
Industries here are the industries PRIAM offers at registration, each with a 4-digit NAICS code.
On 2026-10-21 there are 12, such as 2211 Electric Power Generation, Transmission and Distribution,
2371 Utility System Construction and 6241 Individual and Family Services. Wherever a code
appears, its industry name appears with it. A shortened name always shows the full name when you
hover over it.
Content Health
A read-only health check of the question library: the same checks the developers run before every release. Nothing here is editable; fix what it flags on the Questions and Recommendations tabs.
At the top: - when the check was run, with Refresh to run it again; - Active questions: how many questions are in use; - Coverage gaps: how many industry-and-category pairs have no question. A customer in that industry would see nothing in that category, so aim for 0; - Universal questions (review): questions marked as applying to every industry. That's a claim worth re-checking from time to time, so they're listed for review; - Recommendation issues: problems with the recommendations content, such as an industry with none at all.
Question coverage heatmap: one row per industry, one column per risk category. Each cell shows how many questions that industry gets in that category: - red 0 is a gap; - amber means few questions; - green means many.
The legend shows the range. Hover over a cell for the exact count. Use it to see where an industry is thin; for example, 2211 had only 2 environmental questions before October 2026.
Universal questions: the list of questions to review.
Recommendations: industries whose content still needs writing (Needs authoring), and any other recommendation problems, each marked error (must fix) or warning (tracked).
Questions
Find questions
- Search by question ID or wording.
- Choose a Category.
- Switch between Active only and all (retired questions appear faded).
- The column filters under the headings narrow further:
- ID contains…;
- Type;
- Weight range (min and max);
- Targeting: Any targeting, Universal, Specific codes, Future release, Untargeted;
- Serves <industry>: the questions a customer in that industry actually gets.
Clear column filters resets them. - Click ID, Category, Type or Weight to sort; click again to reverse, and a third time to undo.
The Targeting column shows who gets each question:
| Shows | Meaning |
|---|---|
| Universal (optionally except some codes) | Every industry, apart from any listed exceptions |
| A list of codes | Only those industries |
| future release | Saved, but shown to no one until its industry is added to PRIAM |
| untargeted | A mistake: no targeting is set. Fix it, because publishing is blocked |
Add a question
1. Click New Question.
2. Enter an ID in the form q_lowercase_with_underscores, e.g. q_cyber_mfa_policy. It can't
be changed later.
3. Choose the Category and Type: multiple choice, yes/no or scale.
4. Write the Prompt, the question itself (10–500 characters). Write it so the person filling in
the assessment can answer it.
5. Set the Weight (0.1–2.0). 1.0 gives the question average influence within its category.
6. For multiple-choice and scale questions, add at least two Options, each with a score from
0 to 100. 0 is the safest answer and 100 the riskiest. Four options, from best practice to
nothing in place, work well.
7. Optionally set the Likelihood and Impact hints, used for the risk heatmap.
8. Set who gets it:
- Universal for a question that truly fits every industry. You can still pick industries to
except.
- Otherwise pick the industries under Applies to.
- If no current industry fits yet (e.g. an agriculture-only question), tick Future release.
The question is saved and shown to no one. Leaving the list empty without ticking it is an
error.
9. Click Create Question.
Adding several? Click Save and add another. The form keeps the Category and the targeting, and clears the rest.
New and changed questions reach customers only after you publish with Seed Control.
Edit a question: click the pencil on its row. The ID can't be changed. Your changes are checked when you save.
Retire a question: click the power button and confirm. The question stops being used in assessments started after the next publish. Assessments already under way are unaffected.
Not in the editor yet: linking a question to its specific recommended action (the "recommended because of your answer" line customers see), and switching a retired question back on. Ask a developer for both.
Recommendations
The recommended actions customers see on their results, organized per industry and by maturity level, from Level 1 · Initial to Level 5 · Optimized.
- The list: one row per industry, with its status:
- authored: its own content;
- inherited: shares another industry group's content (the Source column shows which);
- placeholder: not written yet, so it's flagged and can't reach customers by accident.
- Filters: industry code, industry name, Status (e.g. placeholder to find what still needs writing) and Source. Clear filters resets them.
- Edit with the pencil. The form has:
- a tab for each maturity level, then a section per priority (Critical, High, Medium, Low), then a card per action;
- for each action: the Recommendation, its Category, Estimated cost and Timeline (drop-down lists), and its Implementation steps and Success metrics, one per line.
- IDs and removal: each action's ID is fixed. Questions point at these IDs, so a saved action can be edited but not removed. Add action creates a new one, which you can remove again until it's saved.
- Checks before saving: missing fields, text too long, duplicate lines, and a level with no actions are all caught. Problems the server finds appear next to the field they concern.
- Effect and record: changes reach customers immediately, and every save is recorded in the audit log.
- Inherited industries: editing one and marking it authored gives it its own content. The other industries that shared the content don't change.
- Not here: adding a whole new maturity level is a developer task.
Industry Weights
How much each risk category counts toward an organization's overall risk score, by industry. One row per industry (plus Default, used for any organization whose industry has no row), one column per category. - 1.0 is neutral. - 2.0 makes that category count twice as much for the industry. - 0.5 halves it.
Valid values are 0.1 to 3.0.
Reading the table - Rows: each row shows the industry code and its short name. Hover for the full name and the note explaining the row's weights. - Columns: long category names are abbreviated (Env, Fin, Ops, Reg, Rep, Resil, Strat); hover for the full name. - Colors:
| Color | Weight | Meaning |
|---|---|---|
| Green | 0.7 or less | Counts less for this industry |
| Grey | 0.8–1.1 | About neutral |
| Amber | 1.2–1.9 | Counts more |
| Red | 2.0 or more | Counts much more, e.g. Safety for construction |
Change a weight: edit the cell and click Save on that row; the button lights up once the row has changes. - When it applies: a change applies to assessments completed from then on, within about a minute. Results already completed keep their scores. - Category order: the weights also set the order of categories when a customer starts a new assessment, with the most important for their industry first.
Note: weights only took effect for customers from October 2026 (#761). Earlier results were scored with the default weights.
Seed Control
Questions you add or change on the Questions tab reach customers only when you publish them here. Each publish creates a new question-set version.
- Validate Library. This checks every active question and lists:
- Errors, which you must fix first: e.g. a missing field, a score out of range, a duplicate ID, an untargeted question;
- Warnings, which don't block publishing: e.g. two questions in a category with the same wording.
- Seed to Firestore. This button publishes, and is enabled after a clean validation.
- Nothing changed: no new version; the live one stays.
- Questions added or removed: a new minor version (e.g. 1.1.0).
- Only wording or settings changed: a new patch version (e.g. 1.1.1).
- Assessments in progress keep the version they started on, so publishing never changes an assessment someone is filling in.
If publishing is blocked: the only thing that blocks it is an assessment still in progress from before versioning existed. You'll see "A content update is pending: new risk assessments are blocked until a reseed succeeds.", and new assessments can't start until it's resolved. Either wait for those assessments to finish, or click Expire unversioned assessments. That closes only the pre-versioning ones and keeps their answers.
Tip: validate before every publish, even if you think nothing's wrong.
Question Set Versions
Risk Admin → Question Set Versions lists every published version of the question set: - the version number (Live marks the current one), when it was published, by whom, and how (Seed Control, a developer script, automatic, or Before versioning); - how many questions it has, and what changed (+ added, − removed, ~ changed); - how many assessments use it (in progress, completed, closed).
View shows a version in detail: the questions added, removed and changed, the assessments that use it (organization, status, dates, number of answers, but never the answers themselves), and its questions by category. This page is read-only; you publish from Seed Control.
Tenant Admin
Tenants lists every customer organization: - Totals: the overall count, how many are on Starter and Growth, how many are suspended, and how many have no owner email on record. - Per organization: its subscription tier (including any temporary override) and user count.
From here you can change an organization's tier, or suspend and reactivate it. These actions affect a customer directly, so double-check the organization before saving.
Reports
- Risk Content Health opens the Content Health tab described above.
- HIPAA Reports (HIPAA Admin access) shows assessment results: completions, passes and pass rate.
HIPAA Admin
The HIPAA Dashboard gives the totals at a glance: participants invited and completed, pass rate, and certificates issued. Companies lists the companies taking the assessment; Participants lists every participant across companies, with their status.
The HIPAA area manages the HIPAA & Data Privacy Assessment: a knowledge assessment that a company's staff take, which ends in a certificate. It needs HIPAA Admin access.
Training audience
Each company has a Training audience: who its staff are, for example Care Coordinators or
Front Desk Staff. Certificates print it as "has completed the training for
Add participants
On a company's page, Add Participants opens a form with one row per person:
| Field | Rule |
|---|---|
| First name, last name | Required |
| Required. This is the participant's only way to sign in. | |
| Confirm email | Must match the email. Pasting is turned off so the address is really typed twice, which catches typos that would send an invitation nobody receives. |
- Several at once: + Add another participant adds a row (up to 50); × removes one.
- Duplicates are skipped: an address already in the company, or entered twice, is skipped, not treated as an error.
- Summary: afterwards you see how many were invited, which addresses were skipped, and any address whose invitation email couldn't be sent.
New participants show as Invited.
The invitation email
Every new participant is emailed an invitation with: - the company name; - what the assessment covers: privacy principles, confidentiality, secure communication, records handling and protecting health information; - the time limit and pass mark (currently 30 minutes and 80%, taken from the assessment's own settings so they always match); - a Start the assessment button.
If an email couldn't be sent, the participant is still added, and the summary says so. To send it again, delete the participant and add them again.
How attempts work
- Questions: each attempt has a set number of questions (25 by default), drawn at random from the question bank.
- Retakes: a retake shows the participant questions they haven't seen first.
- Pass mark: a participant passes at the mark that applied when the attempt started.
Certificates
A participant who passes gets a certificate, valid for 12 months. They can download it: - right after signing in, where their certificates are listed with Download and the valid-until date, alongside Take the assessment again; - from the results screen of a passed attempt; - on the certificates page.
A participant can only ever see their own certificates.
What the certificate shows: "HIPAA Certification Training" and "HIPAA & Data Privacy"; the participant, their organization and its training audience; the completion date, training hours, score and certificate ID; "Valid 12 months from completion"; the signatory; and a gold seal reading HIPAA Training Certification with the year of completion. It certifies that the training was completed. It doesn't certify that an organization is HIPAA compliant.
Good practice
- Use a dedicated admin account (e.g.
platform@yourcompany.com) rather than your personal one, so access is easy to audit and remove. - Publish in batches: finish a set of question changes, validate, then publish once.
- Write for the reader: customers read your template text, rule reasons and recommendations. Be specific, and avoid internal jargon.
Related documents
- API reference: Platform Admin endpoints
- RBAC matrix: who can access the portal and how it's enforced
- Auth guards (developers)
- Parking lot: operator and developer procedures moved out of this guide
- Policy Management swimlane: the process flow from platform admin to customer to employee
- HOW_TO_USE.md › Policy Management: the customer side