The right access for every teammate.

A two-person founding team can get by with everyone having admin access. A 20-person product organization cannot. Once your team scales past the point where every person needs full reign over every board, you need permission granularity that matches the structure of your team. Team roles in Upvoty give you exactly that, with the right balance of safety and flexibility.

We ship with five built-in roles that cover the workflows of the vast majority of product teams: Owner has full access including billing, Admin manages boards and members, Moderator approves and merges posts, Contributor replies on behalf of the team without admin powers, and Viewer has read-only access to the dashboard. These five cover roughly 95% of teams; for the remaining 5% with bespoke access requirements, enterprise plans support fully custom roles.

Per-board permissions, not global

Permissions in Upvoty are scoped per board, not globally. This matters more than it sounds. A product manager who is responsible for the Mobile board should not automatically have moderation rights on the Enterprise Beta board. A contractor working on a temporary internal project should not see customer feedback on the main public board. Per-board scoping makes those distinctions one-click rather than a major organizational headache.

Combined with private boards, per-board permissions become the foundation for confidentiality. The board where enterprise customers file sensitive feedback is invisible to anyone who is not explicitly granted access, and the audit log captures every time a viewer is added, removed, or has their permissions changed.

SSO provisioning and SCIM

For teams that already manage identity through an IdP, role mapping flows from User SSO. SAML group attributes or OIDC claims can map directly to Upvoty roles, so when someone joins your engineering team in Okta, they automatically become a Moderator on the engineering board in Upvoty, no manual provisioning. Enterprise plans add SCIM for full lifecycle automation: when a person leaves your company, their Upvoty access is removed in the same step.

The audit log is not optional

Every privileged action, approving a post, merging two posts, changing a status, granting a role, is captured in Upvoty's audit log with the actor, timestamp, target, and outcome. This is the single most important feature when something goes wrong: a customer complains their post was wrongly deleted, an investor asks who approved a sensitive piece of feedback to be made public, an internal review needs to confirm role assignments at a particular point in time. The audit log makes all of these straightforward instead of impossible.

For teams that want programmatic access, the audit log is exposed through the Upvoty API, which means you can pipe it into your SIEM or compliance tooling alongside the rest of your operational data. Combine roles, SSO, audit log, and per-board scoping and Upvoty becomes safe to deploy in organizations where security questionnaires are part of every vendor review.