How Sleekplan handles end-user accounts

Sleekplan keeps two kinds of accounts completely separate: the admin accounts you and your team use to run the workspace, and the end-user accounts your customers use when they submit feedback, vote, or read your changelog. The short version: your customers never create an account “at Sleekplan.” They only exist inside your own workspace.

​

The two account types

​

Admin accounts

An admin account is a login at Sleekplan for you and your team members. It’s how you manage the backend: the feedback board, the roadmap, changelog, settings, and everything else in the dashboard. Accounts at Sleekplan itself are exclusively for administrative purposes. Every workspace is a fully separate entity, so an admin account gives access only to the workspaces it’s been added to.

​

End-user accounts

An end user is one of your customers. They interact with your widget or public portal to post ideas, vote, comment, and follow your changelog. These accounts do not exist at Sleekplan itself, they live only inside your own workspace. You’ll find every end user under Customers in the dashboard, along with their activity such as posts, votes, and comments.

​

Why your customers don’t sign up at Sleekplan

Think of Sleekplan as a service provider that runs the feedback application on your behalf. Your end users are your customers, not ours:

• Their data stays within your area of accountability. We act as the processor that stores and displays it for you.
• We never reach out to your end users directly. The only messages they receive (like new-reply or status-update notifications) are sent under your company’s name and branding.
• Many end users won’t even realize they’re using a separate application, especially when you connect single sign-on so they’re signed in automatically with their existing account on your product.

​

How end users get an account

End users are created automatically the first time they interact with your board, so there’s nothing for you to set up per user. There are a few common paths:

• They sign in through the widget with an email address (and optional name) the first time they vote, post, or comment.
• Single sign-on passes their identity from your product, so they’re recognized instantly with no separate sign-up. See the multi-language SSO guide in the developer docs.
• You add feedback on their behalf, which creates the user for them. See Post on behalf of someone else.