Anaplan user licensing rests on named people. The SaaS Subscription Agreement defines an Authorized User as a named person supplied with access by the client within the usage limits of the Order Schedule, and forbids sharing a subscription between individuals.[1] The product documentation turns this into licence types, seats and administration screens. This article describes what Anaplan’s public documents say, and where they stop. They do not publish a table that defines each licence type, a price per seat, or which actions each type permits, so a customer must read its own Order Schedule for those.
Editions
Licence types. Anapedia says that “each license type you purchase has an allocated number of seats you can assign to users”, and that the Summary page shows how many seats have been assigned and how many remain for each type.[2] The example image on that page shows a type named Planner, with 73 of 70 seats assigned, and the page adds that what displays “depends on your license terms and purchases”.[2] The licence report page names Planner, Contributor and Participant when describing the report, and says a user with the Participant licence who carries out actions associated with a Planner is marked non-compliant.[3] No Anapedia page reviewed lists the permitted actions of each type, so the mapping between a type and the right to build models, edit data or only view data is not public.
Roles are not licences. Anaplan separates permissions in the product from licence entitlements. The page builder role, for example, can be assigned only by tenant administrators on the Access Control, Assignments screen, and the user must already have access to at least one model in the tenant.[4] The Workflow Owner role is the administration role for creating tasks and workflow templates, and Workflow itself is “an entitled service that must be bought separately”.[5] The AI Admin role gives access to Agent Studio.[6] The documents present roles and licence types as separate settings, so an inventory needs both lists.
Anaplan XL Web. Anaplan XL Web is licensed by named user “rather than the number of concurrent users”. Each user, identified by LAN credentials, is allocated access the first time they connect. If the maximum number of users has been reached, the user receives a message that the users are full. Only users with a role membership can connect, and a user with several browser sessions is counted once.[7] A licence is released by deleting the user from the Users list with the SQL Repository Administration application, and more users are obtained by contacting Anaplan support.[7] See Anaplan XL Web named user.
Metrics
| Metric | Definition | Source |
|---|---|---|
| Authorized User | Named person with credentials, within Order Schedule limits | Agreement 1.5[1] |
| User licence type seat | One assignable seat of a purchased licence type | Anapedia[2] |
| Visiting user | User from another organisation invited to the tenant | Anapedia[8] |
| Anaplan XL Web named user | User allocated on first connection | Anapedia[7] |
Visiting users. A visiting user “may be from a partner organization” and is added to workspaces in the company’s tenant.[8] User administrators can invite visiting users and assign them a licence, in the same way as internal users.[2] A partner, consultant or contractor invited this way takes a licence from the customer’s own seats, so a customer should count them in its inventory. The Agreement allows access for the client’s internal business purposes and prohibits access by individuals who are not Authorized Users; the Fair Use Policy counts contractors acting for the client among Client Employees.[1][9] How a third party’s use, for example by an implementation partner, is treated depends on the Order Schedule, which is not public.
Counting / floors
Assignment. User administrators can assign and manage licences for internal and visiting users in the Administration console. A licence can be assigned when a user is created or invited, and modified afterwards, and the bulk user import and export endpoints in the Administration API can create users and update their licence information.[2]
Automatic assignment. If internal or visiting users do not have a licence in the tenant, “they are automatically assigned the lowest-level user license per your contract”, the type can be changed afterwards, and “there’s no penalty if the auto-assignment pushes you over your license limit”.[2] The same text appears in the licence management reporting page.[10] Two cautions follow. First, the statement is about platform behaviour, and the Agreement still says that excess usage over a limit is invoiced through an Order Schedule after thirty days.[1] Second, seats assigned by default can inflate the count of the lowest-level type, which is a reason to review users who were never given an explicit licence.
The Summary page. The Administration console’s Summary page displays purchased licences and their usage. User administrators have read and write access and can use a Manage users link to change licence and other user details, while tenant administrators and view administrators have read access.[10]
User licence report. The user licence report shows which licences are assigned to each user and whether the user’s platform activity is compliant with the assigned licence over a trailing twelve-month period.[3] It is in limited availability, and Anapedia asks customers to speak to their account executive.[3] The report has two parts.
- An overview with a line graph for each licence type of seats assigned over twelve months against seats available, coloured green when within the limit, yellow when about to exceed it and red when exceeded. A red warning icon means a user with that licence executed non-compliant actions.[3]
- A table of active users for the period, plus disabled users who still have licences or activity, with the assigned licence, a licence history icon and a status of COMPLIANT or NON-COMPLIANT. A non-compliant status identifies users “whose actions on Anaplan don’t match the permissions granted by their assigned license”.[3]
Anaplan presents the report as a way to assess compliance, optimise licence allocation by upgrading users who act over their licence, and inform renewal discussions.[3] Because the report compares each user’s actions with the assigned licence, reviewing it before a renewal is as useful as counting seats. The table contains each user’s name and email address, so access should be limited to administrators.[3]
Floors. The purchased quantities cannot be decreased during the Subscription Term.[1] Subscriptions may be reassigned when an individual leaves or changes job, which allows seats to be recycled but not reduced.[1]
Virtualization & partitioning
Licence assignment and the Summary page are tenant-level Administration functions. A tenant contains the client’s workspaces and authorized users, and workspace administrators assign roles within models.[11] Anapedia describes a tenant setting that limits adding and removing users to user administrators in the Administration console. It is off by default, so workspace administrators can add or remove users from within a model unless a tenant administrator turns the switch on.[12] This matters for control: with the setting off, a workspace administrator can add users, which can increase licence consumption without the central licence owner’s involvement. User administrators can also use the SCIM API to add or remove users regardless of the switch.[12]
Cloud / BYOL
User licences are subscription rights within a hosted service, and they are not transferable between organisations. The Agreement lets a client reassign a subscription to a replacement user but not to share it, and it prohibits making the service available to those who are not Authorized Users.[1] If a company is split or sold, the Agreement’s assignment clause allows the agreement to move as a whole to an Affiliate or in a reorganisation, but it does not describe splitting seats.[1] Such a case requires negotiation with Anaplan.
Programs
Contract-driven terms. Seat counts, types and prices live in the Order Schedule. The documents reviewed do not describe a public volume-discount, true-down or named-user transfer programme.
Practical review steps. A review before renewal can follow this list.
- Export the Summary page for seats purchased and assigned per type.[10]
- List internal and visiting users with their licence history, and find those with an auto-assigned lowest-level licence.[2]
- If the licence report is available, review all NON-COMPLIANT users and decide whether to upgrade their licences or restrict their roles.[3]
- Check that Workflow Owner, page builder and AI Admin roles are held only by users whose entitlements cover them.[4][5][6]
- For XL Web, compare the number of users allocated with the licence maximum.[7]
Out of scope
This article does not give per-type permission matrices, prices or negotiated terms. It does not cover model-level access control, SSO or SCIM configuration beyond the points that affect licence counts.