Summary and recommendation
UXPin user management can be run manually, but complexity usually increases with role models, licensing gates, and offboarding dependencies. This guide gives the exact mechanics and where automation has the biggest impact.
UXPin is a design and prototyping platform built around a fixed role model: Owner, Admin, Editor, and Viewer.
There are no custom roles, and permissions apply account-wide or per-project depending on the role assigned.
Like every app that charges per editor seat, the cost exposure grows quietly when inactive accounts go undetected.
Team management lives at app.uxpin.com/team, accessible via the account avatar menu in the top navigation.
Quick facts
| Admin console path | Top navigation → Account menu (avatar) → Team Management |
| Admin console URL | Official docs |
| SCIM available | No |
| SCIM tier required | Enterprise |
| SSO prerequisite | Yes |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Owner | Full account control: billing, plan changes, all admin actions, can transfer ownership. | Cannot be removed by other admins; only one Owner per account. | All paid plans | Counts as a paid seat | Ownership transfer requires explicit action by the current Owner; leaving the account without transferring ownership can lock billing access. |
| Admin | Invite and remove members, change member roles, manage team settings, access all projects. | Cannot change billing or plan; cannot remove the Owner. | All paid plans | Counts as a paid seat | Admin role grants access to all team projects regardless of individual project sharing settings. |
| Editor | Create, edit, and publish prototypes; comment on projects they have access to. | Cannot manage team members, billing, or account settings. | All paid plans | Counts as a paid seat | Each Editor consumes a full paid seat; adding Editors beyond the plan limit triggers an upsell or additional charge. |
| Viewer | View and comment on prototypes shared with them; no editing capability. | Cannot create or edit prototypes, manage team, or access billing. | Viewer access is available on plans that include stakeholder/viewer seats; exact plan gating should be confirmed against current pricing page. | May not consume a full paid Editor seat depending on plan; verify on current pricing page. | Viewer seats may be limited or counted differently per plan tier; confirm current plan terms before bulk-adding Viewers. |
Permission model
- Model type: role-based
- Description: UXPin uses a fixed set of predefined roles (Owner, Admin, Editor, Viewer). Permissions are assigned at the role level and apply account-wide or per-project depending on role. No custom role creation is available.
- Custom roles: No
- Custom roles plan: Not documented
- Granularity: Role-level only; no field-level or object-level permission overrides. Project-level sharing controls which Editors and Viewers can access specific projects, but role capabilities are fixed.
How to add users
- Log in as Owner or Admin.
- Navigate to Team Management (app.uxpin.com/team or via Account menu).
- Click 'Invite Members' or 'Add Member'.
- Enter the invitee's email address.
- Select the role to assign (Editor, Viewer, Admin).
- Click 'Send Invitation'.
- Invitee receives an email and must accept to join the team.
Required fields: Email address, Role selection
Watch out for:
- Invitations expire if not accepted; a new invite must be sent if the link lapses.
- Adding an Editor beyond the current seat count may immediately trigger a billing change or block the invite depending on plan settings.
- Invitees must have or create a UXPin account to accept the invitation.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | No | Not documented |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | Yes | Enterprise |
How to remove or deactivate users
- Can delete users: Yes
- Delete/deactivate behavior: UXPin help documentation describes removing (deleting) a member from the team via Team Management. Removed members lose access immediately. Whether their projects and assets are retained under the team account or deleted is not explicitly detailed in publicly available help docs; verify with UXPin support before removing users with critical assets.
- Log in as Owner or Admin.
- Navigate to Team Management (app.uxpin.com/team).
- Locate the member to remove.
- Click the options menu (three dots or 'Remove') next to the member's name.
- Confirm removal.
| Data impact | Behavior |
|---|---|
| Owned records | Not explicitly documented in publicly available help articles; projects created by the removed user may remain in the team account but ownership transfer behavior is unconfirmed. |
| Shared content | Shared prototypes the removed user had access to remain accessible to other team members with appropriate permissions. |
| Integrations | Not explicitly documented. |
| License freed | Removing a member frees the seat, making it available for a new invite on the same billing cycle. |
Watch out for:
- Data ownership behavior after member removal is not explicitly documented in public help articles; contact UXPin support before removing users who own critical projects.
- Removal is immediate; the user loses access as soon as the action is confirmed.
- If the account is on annual billing, the freed seat may not result in a prorated refund; verify billing terms.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Editor seat | Full create/edit/publish access to prototypes; counts toward paid seat limit. | Varies by plan: Essentials ~$6/user/mo, Advanced ~$29/user/mo, Professional ~$69/user/mo, Company ~$119/user/mo (all billed annually; verify current pricing at uxpin.com/pricing). |
| Viewer seat | View and comment on shared prototypes only. | Seat cost and whether Viewers consume paid seats varies by plan; verify on current pricing page. |
- Where to check usage: Team Management page (app.uxpin.com/team) shows current members and seat consumption.
- How to identify unused seats: Review member list in Team Management for users who have not accepted invitations (pending status) or who have not logged in recently; UXPin does not surface a last-login timestamp in the standard UI per available documentation.
- Billing notes: Plans are billed per Editor seat annually or monthly. Adding seats mid-cycle may be prorated or billed immediately depending on plan; confirm with UXPin billing. Enterprise pricing is custom and requires contacting UXPin sales.
The cost of manual management
UXPin does not surface last-login timestamps in the standard Team Management UI, so identifying unused Editor seats requires manually cross-referencing invite status and member activity.
Annual billing compounds this: removing a member mid-cycle does not automatically generate a prorated credit, and adding an Editor beyond the current seat count may trigger an immediate billing change or block the invite entirely. Viewer seat costs are not clearly surfaced during the invite flow, creating a second vector for unplanned spend.
What IT admins are saying
Community evidence is not specific enough to quote or summarize yet for this app.
The decision
Every app with a fixed role model and no activity visibility creates the same operational pattern: periodic manual audits become the only reliable control. UXPin offers no way to scope permissions more narrowly than the predefined Owner, Admin, Editor, and Viewer tiers. Before adding Viewers in bulk, verify how your current plan counts those seats.
Before removing any member who owns projects, contact UXPin support - data ownership behavior post-removal is not explicitly documented in public help articles.
Bottom line
UXPin's Team Management covers the basics - invite, assign role, remove - but leaves meaningful operational gaps: no activity visibility, no prorated offboarding credits on annual plans, and no automated provisioning path outside of Enterprise SSO.
For teams running periodic access reviews, every app in the stack that lacks last-login data adds manual overhead, and UXPin is one of those apps. The workflow is straightforward to execute but requires deliberate process discipline to avoid seat sprawl and billing surprises.
Automate UXPin workflows without one-off scripts
Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.
