Sign-in, teams and roles
Sign in, create an org, invite people by email, and control what each person can see and do.
Sign-in, orgs and email invites
Sign in with an email code or Google, name your workspace, and invite teammates by email. They click the link and land in your org.
Why
Machine data is a team sport. The person who wrote the firmware, the person running the test and the person talking to the customer all need to see the same chart. That should take one invite, not a new account setup call.
How it works
Sign up with your email and Plexus sends a 6-digit code, or use Google. On sign-up you name your workspace. That workspace is your org: devices, dashboards, API keys and alerts all belong to it.
To add someone, open Settings → Members and click Invite. Enter their email and pick a role. They get an email with a link that works for 7 days. When they open it and sign in, they join your org. If they're new to Plexus, the sign-up screen already knows which org they're joining and skips creating a workspace of their own.
Using it
Pending invitations show in the Members tab, and you can revoke one before it's used. If you belong to more than one org, switch between them from the sidebar.
Limits
Inviting teammates is part of the Founding 50. On Free, the Members settings stay visible but locked.
Custom roles
Give people the Admin, Editor or Viewer role, or build your own. Separately, limit a person to just the devices they need.
How it works
Plexus separates two questions. The role sets what someone can do. The scope sets what they can see.
There are three built-in roles: Admin, Editor and Viewer. Their permissions are fixed. To change what a role can do, create a custom role. A custom role starts from Editor or Viewer, and you switch individual permissions on or off from there.
Using it
Open Settings → Access. It's one grid: roles across the top, permissions and dashboards down the side. Click New role, name it, and toggle the cells you want. For each dashboard you can set no rule, view or edit per role. A dashboard with no rules is visible to the whole org. Admins can always open and edit everything.
To limit what someone sees, open the Members tab and edit their scope. Pick the devices they can see. Everything else is hidden from them: charts, alerts, events and monitors for other devices. You can also set scope when you invite someone.
Limits
Admins are never scoped. API keys act for the whole org and are not scoped by a member's access. Inviting people and custom roles are part of the Founding 50.