Polotno SDK gives developers full control over how users interact with the editor — who can access it, what features they can use, and how their data is stored or limited. Instead of offering a built-in user system, Polotno integrates directly with yours, letting you define accounts, roles, and access rules however your app requires. User management spans across the client-side editor, backend rendering, and automation layers. You can define permissions for editing, exporting, or asset access while tracking usage and enforcing quotas programmatically.
Key features
Bring your own user system
Polotno doesn’t manage accounts — it plugs into your existing infrastructure. You can use your own database, authentication provider, or SaaS backend to store and verify user profiles.
Roles and permissions
Define custom roles (e.g., editor, viewer, admin) and tie them to capabilities such as editing, exporting, or template creation. Permissions can be passed to the SDK at session initialization.
Usage and quota tracking
Track how many designs, exports, or renders each user performs. Quotas can be enforced in your backend before launching the editor or sending rendering requests.
Organization and team structure
For multi-tenant or SaaS setups, users can be grouped under organizations or teams. Each team can have separate asset libraries, templates, and permission sets — ideal for agencies or enterprise workspaces.
Feature gating
Lock or unlock features dynamically based on user plans or tiers. For example, limit premium templates, CMYK exports, or video rendering to specific subscription levels.
Session-based context
Pass session tokens or payloads when initializing the editor. The SDK uses your context to load the correct permissions, templates, and assets for that specific user.
Audit and analytics integration
Hook into Polotno events (open, save, render, export) to track user behavior and gather analytics. Use it to monitor engagement, prevent abuse, or charge usage-based fees.
Self-hosted and cloud flexibility
All user control logic remains yours — even when using Polotno Cloud Render API. Tokens or API keys can be validated on your side before allowing rendering or automation tasks.
Example use cases
SaaS design apps – Manage users, teams, and subscription tiers while embedding Polotno editors.
Enterprise systems – Map internal user directories or SSO systems to define editing permissions.
Agencies and resellers – Manage multi-client setups with isolated asset libraries and roles.
Automation platforms – Track render usage per user or account for metered billing.
Education and training tools – Limit editing time or template access per student or group.
Developer benefits
Complete ownership of user data and access logic.
Role-based feature control and dynamic session management.
Integrates with any authentication, database, or billing system.
Scales across both single-user and multi-tenant environments.
Fully compatible with cloud or self-hosted deployments.
FAQs
Does Polotno have a built-in user system?
No. You implement user accounts, and Polotno consumes your authentication and permission logic.
Can I limit usage per user or plan?
Yes. You can track and enforce limits via your backend using event data or API requests.
Does Polotno support organizations or teams?
Yes. You can group users, isolate their assets and templates, and define shared permissions.
Can I integrate analytics or billing?
Yes. You can use Polotno’s event hooks to monitor activity and connect it to analytics or billing systems.
Does this work with cloud rendering?
Yes. You can validate cloud rendering requests against your own user data before allowing exports.