Client Portal security

A client proves they are the person you invited in one of three ways: with the button in their invitation, with a link or six-digit code emailed to the invited address, or with a Magpie account. Each link and code works once. Being a Contact, or sharing a company name, gives no access.

A code works only in the browser that asked for it, and 5 wrong codes use it up. A link is used when its page opens the portal, not when the email arrives, so a mail scanner that checks the link does not use it up.

A Magpie account opens the portal only after it is connected to the client. When you invite a client while client sign-in 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 client sign-in was off gets theirs once it is on. A client can also connect an account at another address by signing in once with the invited address while signed in to that account, in the same browser. 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. Revoking the client's access disconnects it.

A client stays signed in until they sign out, you revoke their access, client sign-in is turned off, or 365 days pass without a visit. Their session is separate from a Magpie member's sign-in.

Every client request checks that the portal is not archived and has client sign-in on, 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 client sign-in, to stop access.

For security concerns, Contact support.