Client Access & Incident Visibility - Invitations, Roles & the Publish Toggle

Overview

MyProtektor uses a single app for all roles, there is no separate client portal. Clients and LiteClients download the same app as guards and admins. What they can see is controlled by their role.

This guide covers what client-facing roles can access, how site assignment works, and how the publish toggle controls incident visibility.

---

Client Roles

MyProtektor has two client-facing roles:

Role	Level	What they can see	Panic button
LiteClient	0	Published incidents, plus any incidents they personally reported. If linked to a site, they can also view published incidents for that site.	Yes, 1 included panic per billing cycle, then additional prepaid credits
Client	1	Published incidents and assigned-site visibility inside the same app	Yes, included

Both roles use the same app. Neither role can see:

• Draft or unpublished incidents
• Guard locations or tracking data
• Internal notes or operational comments
• Analytics, reports, or team management
• Other clients' data

---

Inviting and Linking Client Users

1. Go to Settings > Organization > Invites in the web dashboard
2. Click Invite Member
3. Enter the person's email address
4. Select the role: Client
5. Send the invitation

The person receives an email with a link to create their account. Once they sign in, they see only what their role permits.

Site assignment: The site's Clients tab can hold both Client and LiteClient accounts. Any client-facing user assigned there can see that site's published incidents. To manage this, open the site's detail page and use the Clients tab.

LiteClient onboarding: LiteClient accounts do not come from the standard organization invite role selector. They follow the dedicated LiteClient signup/subscription flow and can then be linked to site visibility where needed.

---

The Publish Toggle

When a guard files an incident report, it enters your internal workflow. Admins see it immediately and can investigate, assign guards, and update the status.

Clients see nothing until you publish.

To publish an incident:

1. Open the incident detail
2. Find the Publish toggle
3. Switch it to Published

The incident now appears in the client's app, for clients assigned to that incident's site. You can unpublish at any time by toggling it back.

What publishing does

• Makes the incident visible to Client and LiteClient roles
• Shows the incident type, severity, status, and any public details
• Does NOT expose guard names, internal notes, or assignment details to clients

What publishing does NOT do

• It does not send a push notification to clients (they see it when they open the app)
• It does not make the incident public on the internet, only visible to authenticated users with the correct role

---

LiteClient Panic Credits

LiteClients can use the panic button, but on a credit model:

• 1 free panic per billing cycle (included with the R25/month subscription)
• Additional panics require prepaid credits purchased through the app
• Credits come in packs of 1, 3, or 5, priced by the security firm
• This is NOT a call-out rate. It is a platform access fee for emergency alerting

When a LiteClient triggers a panic, the alert reaches your control room with the same data as a guard's alert: GPS, identity, device status, and timestamps.

---

Related Solutions

• Client Communication -- the full solution page covering client visibility and the publish workflow

---

Common Issues

Client says they can't see any incidents: Check two things, (1) Is the client assigned to the correct site? (2) Are incidents for that site published?

Client asking for more detail than shown: Clients see only what is published. If they need more information, an admin should update the incident's public-facing details before publishing.

LiteClient panic button greyed out: The LiteClient may have used their free panic and has no remaining credits. They need to purchase a credit pack through the app.