A Dataiku user profile is the attribute that Dataiku uses to count and limit seats in a licence. The Dataiku DSS documentation states that each user in DSS has a single user profile, and that user profile is not a security feature but a licensing-related concept: DSS licences are restricted in number of each profile.[1] Profiles therefore sit beside, and do not replace, the group-based permissions that control access to projects and connections. The same documentation says Dataiku does not guarantee that a user profile is strictly applied and tells customers to use the regular groups authorisation model for security.[1]
For a software asset manager, profiles are the unit to inventory. A licence file or cloud subscription contains a number of seats for each profile in use, and the count of users assigned to each profile is compared with those entitlements. This article describes the profile names Dataiku documents, how defaults and fallbacks behave, how administrators change profiles, and how profiles relate to the contract definitions of Named User and User.
Editions
Profile availability depends on the licence. The documentation says that the exact definition of the profiles available depends on the DSS licence, that a customer may have other profiles or only some of them, and that questions should go to the Dataiku Account Manager.[1] A Free Edition licence is generated automatically and never needs updating, while an Enterprise Edition customer receives a licence file from Dataiku and a new file at renewal.[7] The seats per profile are therefore a feature of the licence file, not a published edition table. On Dataiku Cloud the list of profiles and the number of seats for each profile depend on the subscription.[3]
Metrics
The metric is a seat per user profile (User profile seat). One user holds one profile at a time, so the seats needed for each profile follow the users assigned to that profile.[1]
Current profiles
The Dataiku DSS 15 documentation lists these profiles as “some of the possible profiles”.[1]
| Profile | What the documentation says it can do |
|---|---|
| Full Designer | Access to all Dataiku features |
| Data Designer | Most visual features, but not coding (Python/R) features nor some advanced AI and ML features |
| Advanced Analytics Designer | Most features, except some advanced coding capabilities |
| Governance Manager | View projects and handle artifacts and sign-off processes in Dataiku Govern |
| AI Consumer | Access dashboards, workspaces and webapps, and run Dataiku Applications created by Designers |
| AI Access User | Only webapps that have been made available to them, such as Agent Hub |
| Technical Account | Technically all features, but may only perform administration and assistance tasks, not productive work; can also be used as service accounts to run scenarios or webapps |
The Technical Account description matters for service identities: the documentation says a Technical Account can run scenarios or webapps as a service account, but it is described as an administration and assistance profile rather than one for productive work.[1]
Older profiles
Older customers may still hold older profile names. The documentation lists Designer (full access), Data Scientist (same as Designer), Data Analyst (most visual features, no coding or AI/ML features), Reader (read project content, dashboards and webapps, no modification), Explorer (Reader capabilities plus running Dataiku Applications and creating dashboards and insights from existing objects) and Platform Admin (all features technically but only administration and assistance tasks).[1] The Platform Admin entry adds that, despite the name, granting that profile does not automatically grant administration rights.[1] The distinction also appears in the Govern product: a DSS 14 release note renamed the “Govern Manager” global permission to “Govern Architect” to avoid confusion with the “Governance Manager” user profile.[9]
Counting and floors
No public document sets a minimum number of seats. Counts and any floors are set by each licence file or Order. The License Terms define a Named User as a User identified individually by name, registered and distinct from concurrent Users, and state that counts refer to Named Users and not concurrent users.[6] They also limit substitution: a Named User may be replaced once per calendar year, or when the individual leaves the Customer or their role or responsibilities change, and further substitutions need Dataiku’s consent, which is not to be unreasonably withheld.[6] The same definitions apply to the contractual User: any employee or contractor of the Customer or its Affiliates that the Customer allows to use the Software.[6]
Three behaviours affect counts in practice:
- No profile means Reader. If a user has no profile associated, the user defaults to the Reader profile and cannot modify anything, whatever their group status.[2]
- Profiles can block actions. When an action is denied because of the profile, the user sees a “Your user profile does not allow …” message and the profile has to be raised.[2] The documentation says the “Data Scientist” profile generally has all rights.[2]
- Cloud guest profile. On Dataiku Cloud, if no seat of the chosen profile is available when a user joins, the user receives the guest profile, which prevents access to the instance until another profile is granted.[3]
Virtualization and partitioning
Profiles are per user, not per machine, so virtualisation and partitioning of the host do not change the seat count. On Dataiku Cloud the profile is defined at space level and the same profile applies on all nodes; access to a node is determined by the groups to which a user belongs, not by the profile.[3] Self-managed customers with several instances should check their licence file and Order for whether seats are shared across instances, because the public documents do not say.
Cloud and BYOL
On Dataiku Cloud, an administrator chooses the profile when inviting or provisioning a user, and can edit it later from the Users and Access Management panel in the Launchpad.[3] The Launchpad also has a Subscription and Plan panel with details of the current plan.[4] The Cloud Terms let the customer provision and manage User accounts and hold it responsible for its Users’ compliance.[10]
On a self-managed instance, the administrator uses Administration, Security, Users, selects the user, changes the user profile and saves, after which the user reloads the browser tab for the change to apply.[2] Administrators can view licence information, including features and quotas, in the Administration menu License tab.[5]
Programs
Profile seats connect to other entitlements. Every paid Designer seat benefits from Monthly Included Usage for AI Services, which is specific to each Designer and not poolable across developers.[8] Because the included usage is attached to paid Designer seats, the number of Designer seats is relevant to AI usage as well as to feature access. See Monthly Included Usage and LLM Mesh and AI Services.
Compliance and audit
The License Terms let Dataiku ask for a verification certificate within 30 days, signed by a senior compliance officer, confirming that use complies with the agreement including the Scope of Use, and charge excess use at the Order rates.[6] Since profiles are described as a licensing concept that Dataiku does not guarantee to enforce, administrators can compare the list of users and profiles with the licence information shown under Administration.[5]
Out of scope
This article does not cover the contents of any customer’s licence file, the price of any profile, or group-based permissions in DSS. It does not describe the older profile names beyond what Dataiku documents, and it does not list profile entitlements for legacy editions that are no longer sold.