Just as the title states, is there a way to stop the new user notification from Birst? We use Mingle to SSO users and don't want to them trying to sign in and change passwords, etc. when we create their account in Birst.
Is this Birst implementation an Accelerator Analytics Content which should have SAML configured?
The SAML configuration provider would be a Ming.le URL.
Were these already Birst users prior to an Accelerator Analytics Content login initiated through Ming.le creation (ie. email used as Birst login)?
Not sure exactly, but yes we do use SAML for configuration
This is when a new employee joins the company. We have to set them up in Mingle and then add them to the list of users in Birst. We use the same email for both. The email triggers automatically when the Birst user is added
This sounds strange. When users get created via IFS role assignments - based on the SecurityBOD that gets triggered, you should not receive a welcome mail from Birst.
Can you elaborate a bit on what you actually do? Are you creating the Birst users 'manually' after the Ming.le users?
Yes, I am creating new users manually after they have a Mingle account, using the same email / username. (To be fair, I'm not sure if there is an ideal way to automate it, as all users have access to different Birst spaces, CRM, ERP, etc. depending on who they are)
@drosen
Please review the attached document. You don't and shouldn't manually create ids in Birst when created in Ming.le and to Pierre's point of creating a BOD.
.[View:/cfs-file/__key/communityserver-discussions-components-files/602/Adding-Custom-Roles-for-Prepackaged-Birst-Content-_2800_2_2900_.pdf:103:112]
So, if you have Birst provisioned as part of the CloudSuite then you should have a connection point as well as two Data Flows in ION.
The whole purpose of this setup is to automatically create Birst users based on the role they're assigned to. This works for both Birst roles (User and System-Administrator) as well as the roles for the pre-built content. In case of M3 it'd be something like M3AFABBIRST - User | M3AFABBIRST - Model Administrator etc.
Unfortunately the space group assignment based off IFS roles is only working for pre-built applications. If you want to use IFS for custom spaces you'd have to use Account Groups or maintain space assignments manually.
Keep in mind that you cannot combine Account Groups and Spaces Groups in catalog permissions at this point.
Right now, we don't really do "role" based security, rather user based because we don't have blanket roles that apply to many people, and we are currently taking advantage of space groups rather than account groups. This is definitely something to explore though if we ever move more in that direction. Thanks for the info!
