Skip to main content
Solved

Automatically assign users to teams/group

  • December 9, 2024
  • 4 replies
  • 162 views

SMoore 6774a9 wcskids
Forum|alt.badge.img

Hello,

 

Is it possible to assign a user to a team and/or a role in IncidentIQ?

 

I do see that setting up a User rule is very limited with the new permissions model. I’ve also found that if I use the conditions within Permissions, that I still cannot automatically add a user to a team or role based on certain conditions.

 

Any ideas/suggestions?

Best answer by jclark

The use of syncing a group from your SSO to a team is nice, but it doesn’t cover everyone’s use cases/needs. I created this idea a long time ago to try to assist with that.
 

 

4 replies

Forum|alt.badge.img+5
  • Contributor
  • December 9, 2024

If you are using an SSO like Google SSO or similar, you can have it assign users to teams and roles from there based on OUs. From there, you can have permissions set up based on teams. As far as I’m aware, there isn’t a user rule/rules that can assign based on criteria of new users without using an SSO. There are instructions on how to use that in the SSO setup Knowledge Base articles. This would be really helpful however.


Kathryn Carter
Forum|alt.badge.img+18
  • Community Manager
  • December 10, 2024

@SMoore 6774a9 wcskids Thank you for submitting your question to our community! 😄

I would suggest creating your teams via SSO and then mapping them to iiQ. Any updates you make on the SSO end will be updated in iiQ during your nightly sync. Here is the KB Guide to get you started: 

 


Forum|alt.badge.img+16
  • Specialist
  • Answer
  • December 16, 2024

The use of syncing a group from your SSO to a team is nice, but it doesn’t cover everyone’s use cases/needs. I created this idea a long time ago to try to assist with that.
 

 


SMoore 6774a9 wcskids
Forum|alt.badge.img

The use of syncing a group from your SSO to a team is nice, but it doesn’t cover everyone’s use cases/needs. I created this idea a long time ago to try to assist with that.
 

 

I up-voted! This would be more beneficial for our use-case opposed to SSO.