#11033 Need help understanding FAS => GitLab permissions
Closed: Fixed with Explanation a year ago by kevin. Opened a year ago by duffy.

Describe what you would like us to do:


I just need some guidance in how FAS and GitLab permissions interact.

  • If a FAS user is a member of designteam-admin, they get "owner" status in GitLab for Design, correct?
  • If a FAS user is a member of designteam, they get "developer" status in GitLab for Design?

My question:
Is there a way to assign "maintainer" status in GitLab via FAS? Right now I've been doing it manually, but it gets removed at regular intervals (I guess when there's some kind of automated sync between the two systems.)

This wouldn't be an issue but for folks who make commits to the repo, GitLab's default setting for protected branches is causing some havoc. It would be easiest to just assign maintainer status for those folks who should have permissions to push to the repo (and leave everyone at developer by default to be able to work on issues and file MRs.)

When do you need this to be done by? (YYYY/MM/DD)


No rush but it's causing some havoc and I'm not sure what's going on. I would be greatful for a little time from anyone who knows how this works who could set me straight, whenever is convenient for them!


If a FAS user is a member of designteam-admin, they get "owner" status in GitLab for Design, correct?

yes, and anyone not in that group is removed from owner.

If a FAS user is a member of designteam, they get "developer" status in GitLab for Design?

yes, and anyone not in that group is removed from developer

Is there a way to assign "maintainer" status in GitLab via FAS

Yes, we would need to make a new group... designteam-maintainer or the like and link it to maintainer. Shall I do that?

Metadata Update from @kevin:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: low-trouble, medium-gain, ops

a year ago

@kevin That would be fantastic! Thank you so much!!!

ok. I made the group, made you a manager/sponsor of it, and linked it on gitlab. :)

Let us know if there's anything else you need!

Metadata Update from @kevin:
- Issue close_status updated to: Fixed with Explanation
- Issue status updated to: Closed (was: Open)

a year ago

Login to comment on this ticket.

Metadata
Boards 1
ops Status: Backlog