Giving clients portal access
Let your client toggle their own switches from the portal without seeing your other clients' projects.
The client portal at portal.dynamik.app is where your client signs in to see their projects, invoices, estimates — and now, their switches.
How portal access works
A switch is visible to a portal user when all of the following are true:
- The portal user's account is linked to a
ClientContactrecord - That contact belongs to a
Clientin your company - The switch's project belongs to the same client
In practice: when you create a portal user for Dencorp and the switch is on a project under Dencorp's account, that portal user sees it. They cannot see any other client's switches.
Portal users are READ + TOGGLE only. They cannot add, edit, delete, or see MQTT credentials. They cannot see your staff names — actions by your team show up as "dynamik.app team" in their activity log.
</div>
-
1
Open the Client record in dynamik.app (Contacts → Clients → click the client).
-
2
Go to the Contacts tab → click Add Contact if there isn't one yet, or open an existing contact.
-
3
On the contact's row, click Invite to portal.
-
4
Enter the contact's email address.
-
5
dynamik.app sends them an invitation email with a magic-link login.
-
6
When they click the link, they set a password and they're in.
After login at portal.dynamik.app, the client clicks into a project and sees a Switches section at the top with:
- Each switch as a coloured row (green = ON, grey = OFF, orange = Offline)
- A Turn on / Turn off primary button for each
- A Recent activity card listing the last 20 actions
The activity log on the portal is anonymised — actions by your staff appear as "dynamik.app team" without their real names. The client sees their own actions as "You" and physical button presses as "External (physical button or schedule)".
</div>
For v1, a portal user with access to a client sees all switches across all of that client's projects. We'll be adding per-switch granular permissions in a future release.
If you need to hide one switch from a specific portal user today, the workaround is to move that switch to a separate project that the portal user isn't linked to.
Next: Troubleshooting.