Best approach to setting the User Manager in a flow, run by a non admin user?

johnathan151613

I have a flow where I'm trying to create a user, then set who that user's manager is. In development this was not an issue, and this flow works properly. However when users began to use this flow, we found out that it would not complete unless the user running the flow is a Decisions Administrator. The account can be created no problem, but when creating the relationship between the new account and the manager, we receive an error stating that {user} is not authorized to get account by Id. We have tried changing the context of the flow to system, and even creating the Relation datatype, but we keep encountering this error while running when users aren't an administrator. What can be done here?

jacob_Decisions

Unfortunately, this is expected behavior. Decisions does not support non-admin users making changes to the "relation" data type, which is how Managers associated with users are handled. This is for security reasons, and should not be attempted to be bypassed. The error having to do with The user is not authorized to get account ID is because that user is not an administrator. The best workaround we are able to suggest is reconsidering the current design, in favor of a design where only those who are administrators can set "manager" relationships on accounts, and restrict use of this flow to users who have an organizational need to be administrators within the Decisions platform.