Why you’re here
Admin is where you get control and scalability without adding friction, and Users is the starting point. Bluplai is a shared space between your team and your customer, so who has a seat and what role they carry is the first thing to get right. You can onboard a partner in minutes with access only to relevant modules, or bring in a customer-side user with a scoped Viewer role for collaboration without overexposure. That reduces onboarding time by 50%+ and minimizes permission errors — governance without slowing execution. Control and simplicity can coexist — and scale together.What you’ll see
At the top, four counters summarise the workspace: Team Members, Admins, Active Permissions, and Modules. Below the tab row, each member has a card with their name, email, a role badge (Admin, Editor, Viewer, or a custom role like “No pulse”), a role dropdown, and a trash icon to remove them. Use Invite Member in the top right to add someone by email. Change a role inline with the dropdown on the right of each row. The role you pick here is the member’s default across the workspace; fine-grained access per module lives on the Permissions tab.When to use it
- A new hire joins Sales, CS, Marketing, or Partners and needs a seat
- Someone changes team and their default role needs to shift
- A contractor’s engagement ends and you need to revoke access
- You want a quick headcount of admins vs. editors vs. viewers
Inviting a member
Why you’d invite one
Every person with a seat in Bluplai — internal teammate or customer-side collaborator — comes in through this same dialog. Getting the invite right is how you keep the workspace safe: the right email lands with the right role, and everyone else stays out. It’s also the single place where you signal whether someone is internal or external, which shapes how they appear in Permissions.How to invite one
Fill in the details
- Email Address — the email the invite will be sent to
- Company — the company the person belongs to. This helps distinguish internal teammates from external partners in the Permissions list
- Role — the default role for this member: Admin, Editor, Viewer, or any custom role you’ve defined
Inviting a customer-side user
Bluplai doesn’t have a separate customer-invite flow — you bring customer-side users in through the same Invite Member dialog. The Company field is the signal that marks them as external, and the role you pick is how you keep their access scoped.Open the same Invite Member dialog
From
/admin/users, click Invite Member. There’s no separate flow for customers — this one dialog covers both internal teammates and customer-side collaborators.Enter the customer's email
Fill Email Address with the email of the person on the customer side you’re inviting.
Set Company to the customer's company
Fill Company with the name of the customer’s company — not your own. This is how the Permissions list distinguishes internal teammates from external partners, so getting it right here is what makes the split visible downstream.
Pick a limited role
Assign a scoped role so the customer only sees what you want them to:
- Viewer is a safe read-only default for most customer-side invites
- For something more tailored, create a custom role on the Roles tab that only grants access to the modules you want the customer to reach (for example, Plan and Engage) and pick it from the Role dropdown
Customer-side invitations count against your workspace’s license. Each paid seat includes a bounded number of customer/guest invites — the exact figure depends on your plan. If you hit the limit, upgrade the seat or free one by removing an inactive customer user from the Users tab.
What happens after
The invitee gets an email with an accept link (/invite/accept?token=…). Once they accept, they appear in the Users tab with the role you chose and show up in the Permissions list labelled by the Company you set. You can change their role inline from the row or refine their module-level access from Permissions.
Next
Roles
Review the three base roles and build custom roles that map to how your teams actually work.
Permissions
Drill into per-module, per-customer access for every member of the workspace.