We are facing the problem that we have external training that has implications to the correct accesses within Tulip. We utilize SAML integration but could think it would be very beneficial that Tulip, through SAML could take more information easing the immediate and long-term burdens of user management regarding specific APP access.
Just to make sure I have this clear, you are looking to map user attributes to the User Table (or somewhere else) so they are accessible within a trigger?
In talking to the team - It sounds like this isn’t currently possible, but is certainly something we could build.
More specificallly, I am looking to map attributes in an AD or ServiceNow request to a Tulip Table so that we can use these specificities within a Tulip Trigger within an APP.
Hi Joe, thanks for following up. We are definitely still interested in doing this, but we do not have a concrete delivery date yet. What sorts of data are you interested in mapping into User Fields? Perhaps there is another way to solve it now or in the near future.
Essentially we would like to interpret user roles from AD/ServiceNow into the custom fields of the users in order to determine app access. At the moment we are manually adjusting the user rights via tables which either grant or deny access which is a very manual process, but we would like to make this operation smoother and less time consuming.
At the moment in Tulip, if a user has multiple roles the highest authority role is granted and the others are not considered. However typically end users will have access across multiple areas where they should have the same access, and then no access in other areas.
Maybe we could have a call about this if it is not clear?
Just want to chime in here that we have the same issue and would love to have this functionality (related: the recent API poll from @joshuarichard. Pulling attributes via SAML would be preferred, but if we could at least update custom user fields via API, that would make this more manageable)
Hello,
We are using the User Custom Fields to restrict actions in an app for different users. Right now we need to manually keep this up-to-date, so having the ability to use APIs to set custom user fields would greatly help us!
John.
Hello all, as of r285 and LTS13, this problem should be solved. You will now be able to add users to user groups, map users into them via SAML, and then reference those user groups in “if” statements in trigger logic. If you would like a tour of this behavior, happy to set one up. Closing this thread for now.