Roles & Permissions
Roles & Permissions
Understand the default roles and configure custom permissions for your team.
Pluraprint controls what each person can see and do through roles. A role is a named collection of permissions; users can have one or more roles, and they get the combined permissions of all their roles.
Default roles
Every Pluraprint organization starts with four roles, layered from most to least access:
| Role | Typical use | Access |
|---|---|---|
| Admin | Owners, IT/operations leads | Full access to everything: printers, jobs, rules, quotas, users, roles, integrations, and settings. |
| Staff | Lab managers, print operators | Manage printers, materials, and print jobs; review and approve jobs; everything a Member can do. |
| Member | Regular submitters (students, employees, makers) | Submit and track their own print jobs, view printers and materials; everything a Guest can do. |
| Guest | Walk-in or anonymous station users | Minimal station-only access, such as viewing available printers. |
Each role automatically includes everything the roles below it can do, for example, Staff can do everything Member and Guest can do, plus more. You can adjust any of these roles’ permissions to fit your organization, or create entirely new roles.
Viewing and managing roles
Open Roles under the Administration section of the sidebar. The table shows each role’s name, description, a preview of its permissions, and how many users have it.
Creating or editing a role
Select Add Role (or Edit on an existing role) and fill in:
- Name: for example, “Lab Assistant” or “Read-Only Viewer”.
- Description: a short note about who this role is for.
- Permissions: choose individual permissions, organized into groups.
Permissions are grouped by area (for example, “Printers”, “Print Jobs”, “Rules”, “Users”) and you can select an entire group at once or pick individual permissions within it. Hover the info icon next to a permission for a description of exactly what it allows.
How permissions are organized
Permissions come in two scopes:
- Web permissions control what a user can do in the main Pluraprint web dashboard: for example, viewing printers, creating print jobs, managing rules, or administering users and roles.
- Station permissions control what’s available at a kiosk station : a more limited set focused on submitting, reviewing, and managing print jobs and printers from a shared, walk-up screen.
A user (or a Guest identifying at a station) only sees actions and pages they have permission for: anything else is hidden rather than shown-but-disabled.
Common permission areas
| Area | Covers |
|---|---|
| Print Jobs | Viewing, uploading, submitting/rejecting, canceling, prioritizing, and reprinting jobs; owners can configure their own job’s details before submission |
| Printers | Viewing printers, adding/editing/deleting them, clearing errors, controlling a running print (pause, resume, stop), and taking printers out of service for maintenance (mark down, restore) |
| Materials | Viewing and managing the materials library |
| Rules | Viewing, creating, editing, and deleting requirement rules |
| Quotas | Viewing, creating, editing, deleting, and adjusting usage quotas |
| Stations & Station Templates | Viewing and configuring kiosk stations |
| Users & Roles | Managing team accounts and role/permission assignments |
| API Keys | Creating and revoking API keys |
| Integrations | Configuring external integrations |
| Analytics | Viewing fleet/usage analytics dashboards |
| Dispatch Policies | Viewing and updating how jobs are matched to printers |
Tips for setting up roles
- Start from the default roles and adjust them. It’s usually easier than building new roles from scratch.
- Give Staff-level roles permission to view and resolve printer errors and submit jobs to the queue, since they’re typically the people responding to issues.
- Keep Member roles focused on their own jobs: broad print job permissions (canceling or reprioritizing other people’s jobs) are usually reserved for Staff and Admin.
- For shared kiosks used by the public or unregistered visitors, use the Guest role and keep its Station permissions minimal; see Stations for how identification and permissions interact at a station.