wigginsli (Customer) asked a question.
If possible to use different Account Template in different conditions
For example, if user in some particular roles or title is 'Admin', then use Admin account template, other user use normal account template
Related Questions
Nothing found
Loading
Trending Articles
Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA-2022-12: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities Downloading RSA Authentication Manager license files or RSA Software token seed records RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026)
Don't see what you're looking for?
Short answer, no. there are no conditional account templates.
Consider the following approach:
Create a new application in G&L for admin accounts of this specific app with a new account template.
Create a form to request access to this app
Limit the form only to users with particular role or admin in the title.
It is also possible to link more than one account template to the same business source.
And then the product will ask (if request made in the product) which account template to use when executing the form.
Although personally I don't use this approach, because the end user usually don't know the difference on these accounts.
Usually when using "G&L" (as Boris mentioned) it is better to re-think the data model of a big directory, to keep it 1-on-1 for templates.
It is often more easy to "split up" directories (like AD) and have two different business sources for say "normal accounts" (business use) and "admin accounts" (low level environment use)
And if you do it, it is even much easier to lock both roles (and accounts) to "Title=Admin" (or any other trusted source that verifies who a person is).
My personal best approach is to have rolesets for admins of different "Tiers", where I limit the entitlements to belong to an admin-application (which has the correct account template for admins and those admin-entitlement). Meaning that if new roles are created for admins, then you/owner can't make an incorrect configuration of the role. This approach even allows to make "super-roles" which set both admin and normal accounts at the same time during fulfilment.
But there is a trap here when splitting a big business source:
It is very important to give the owners of a Directory/Application a correct view of the state of ALL accounts which give possible logins to their system. With the target to set ownership on all.
Thanks for the answer, however, in our environment we do not use request forms in G&L, as all access requests are managed through our ServiceNow ITSR process. Also, many applications require provisioning both normal and admin accounts, so creating separate “admin” business sources per application would result in a large number of business sources and significant operational overhead.