Make years of customer terms understandable
Once you have legacy versions, custom deals and several products, a plan name no longer describes a customer’s access. Entitler records each customer’s terms, with version history, team roles and control over when customers move.
Explore the example- Export to PDFOn or off, from ProIncluded
- Priority supportOn or off, in Support extras, from ProIncluded
- Support SLASetting, in Support extras, changed from Pro4 hoursPro has 24
- AI creditsMetered, resets each period, changed from Pro2,000 creditsPro has 500
- Team seatsSetting, added in Okafor Studio25 seats
- Shared foldersOn or off, added in Okafor StudioIncluded
- From Pro
- Changed from Pro
- Added for Kai
One customer needs different terms
Kai needs more seats, more credits and a shorter support response time. Compare a versioned custom plan with grants that add to his existing package.
Step 1 of 6: The request
Kai has used Pro for two years. His studio now needs a package outside your standard tiers.
We would like to put our whole studio of 25 on one account before we renew on 28 October. We need 25 team seats, shared folders, 2,000 AI credits a year and a first reply from support within 4 hours. Can you put that together?
- 25 team seats
- Shared folders
- 2,000 AI credits a year
- A 4-hour support reply
ProductionLive- AI credits0 of 1,000 used this periodAccess source Pro, version 1
- Export to PDFYesAccess source Pro, version 1
- Priority supportYesAccess source Pro, version 1
- Support SLA24 hoursAccess source Pro, version 1
Separate changing plans from changing customers
Assign roles based on responsibility. Start with owner, admin, member and viewer, and add your own roles: some edit changes and send them for review, others release them. Each environment’s protection then decides the roles allowed to roll out and change its customers.
- OwnerFull access, including deleting the team. Owners can always roll out.Edit changesApprove and releaseRoll out in test environmentsRoll out in live environments, once listedCustomers in test environmentsCustomers in live environmentsAPI keysMembers and settings
- AdminEverything but deleting the team: plans, releases, customers, API keys, members and settings.Edit changesApprove and releaseRoll out in test environmentsCustomers in test environmentsCustomers in live environmentsAPI keysMembers and settings
- MemberEdit changes and send them for review, roll out in test environments, change customers and manage API keys.Edit changesRoll out in test environmentsCustomers in test environmentsCustomers in live environmentsAPI keys
- ViewerView project data without making changes.Can see everything, change nothing
- FinanceA role you add: edit and release changes, and roll out in the live environments with a protection listing it.Edit changesApprove and releaseRoll out in test environmentsRoll out in live environments, once listed
- SupportA role you add: manage customer subscriptions, grants and usage, and read the catalogue without editing it.Customers in test environmentsCustomers in live environments
These are the defaults. Each environment’s protection can narrow them, and a live environment can require a second person to approve rollouts. Only owners and admins can invite members or change their roles.
Several products, kept apart
Use a separate project for each product's catalogue, with test and live environments for its customers and API keys. Team members retain their role across projects.
- ProjectNotesFree, Pro, Team. 8,420 customers in Production.
- Plans, add-ons and features, edited in changes
- Named releases, with contents that never change
- Customers, in Development and Production
- Secret and publishable API keys
- Tracks such as Beta and All customers, per environment
- Rules for plan changes and billing periods
- ProjectDocsFree, Pro basic, Pro. 2,160 customers in Production.
- Plans, add-ons and features, edited in changes
- Named releases, with contents that never change
- Customers, in Development and Production
- Secret and publishable API keys
- Tracks such as Beta and All customers, per environment
- Rules for plan changes and billing periods
- ProjectFormsStarter (legacy), Pro. 640 customers in Production.
- Plans, add-ons and features, edited in changes
- Named releases, with contents that never change
- Customers, in Development and Production
- Secret and publishable API keys
- Tracks such as Beta and All customers, per environment
- Rules for plan changes and billing periods
More situations larger companies run into
Keep track of long-lived agreements, inherited packages and the teams responsible for changing them.
Three products become one
Several older products have been combined into one, but customers still hold the original plans. Mark older plans as legacy in a change, which closes them to new subscriptions on each track that runs the release, while existing customers keep them. Move customers now or at renewal, and follow the remaining subscriptions by cohort, the customers joining on each version.
More on retiring a planA pilot before the contract is signed
A large customer wants to try shared folders with their team for a quarter. Grant 90 days of access with “Pilot” as the reason. The grant expires automatically unless replaced with an ongoing arrangement.
More on grantsSupport needs a clear view of customer access
Account managers depend on engineers to look up customer access. Open the customer account to review feature access, its source and the subscription activity history.
How support uses itYou have to change billing provider
Your payment provider becomes unavailable and you need to migrate quickly. Keep feature checks in Entitler while your team migrates the billing integration.
More on changing billing provider
Questions larger teams ask
More solutions
Explore all solutions, organised by team, company size, industry and use case.
Try your plans in Entitler
Start with sample plans and customers. Then try a change you expect to make, such as a new tier, a usage allowance or an exception for an early customer. Request an invite to try it with your team.