Client Portal security
How clients open a portal with their Magpie account and what each request checks before it shows them anything.
A client opens a portal with their Magpie account, the one at the address you invited. There is no separate portal sign-in: signed out, the portal's address asks them to sign in to Magpie. Being a Contact, or sharing a company name, gives no access, and a Magpie account at any other address is told it has no access.
When you invite a client while Open to clients is on, or start a client's coaching, Magpie connects the Magpie account at the client's address, and makes one when there is none; a client added while the portal was closed to clients gets theirs once it is open. If the account at the client's address was never confirmed, it opens the portal only once its owner confirms the address, so an account someone else made with the address is not let in. The account only signs the client in. It does not join your team and cannot see anything else of yours.
The Open portal button in an invitation is a sign-in link for that account, and works only while the address it was sent to is still the account's. It signs in only an account nobody has used yet: never signed in to, with no password, passkey, sign-in provider or team. It works once, within 7 days, and only when the Sign in button on the page it opens is pressed, so a mail scanner that checks the link uses nothing. For any other account it opens the portal's address. Revoking the client's access, turning off Open to clients and archiving the portal stop an unused button, and a newer invitation stops the earlier one's. After someone signs in with the button, Magpie emails the account to say so, naming the browser and roughly where; if it was not the client, Sign out of every other browser in Account settings ends that sign-in (Password and two-factor authentication).
After that, a client signs in as anyone signs in to Magpie: with a link and a six-digit code emailed to their address, each usable once within 30 minutes, or with a password, passkey or sign-in provider they added. A code works only in the browser that asked for it, and 5 wrong codes use it up. The portal's sign-in page makes no account, and its email names the portal only to an address that can open it. A client stays signed in until they sign out of Magpie. See Create an account and sign in.
Every client request checks that the portal is not archived and is open to clients, that the client still has access, that the section is on, and that the item is shared. A plan must be shared, not a draft. Signing links and proposal links opened from the portal, and file downloads, go through the same checks.
Clients can change only these: they can tick the steps marked for them in an active plan, record progress on a goal with a target in an active plan, upload files when Files is on, sign signature requests they are a signer of, and open a shared proposal they are a recipient of. Everything else, including your team's steps, is read only.
Internal Contact notes, Issues, project comments and other team work stay private. They are not shown in a portal even when the project or Contact they belong to is.
The portal's address can be known by anyone. Revoke a person's access, or turn off Open to clients, to stop access. Neither signs anyone out of Magpie: the account stays theirs and no longer opens the portal.
For security concerns, Contact support.
Ask Magpie support
Send Magpie staff a question about anything this article does not answer.