This message was deleted.
# questions
b
This message was deleted.
đź‘€ 1
e
@chilly-midnight-76694 Thanks for your question—I totally see how this could be useful. There is no direct and easy way to do this, though I think a workaround should be possible. There might be a few ways to do this, but this is my idea. What you would do is: 1. Create a specific role for this type of users, for example “POC Admin” 2. When setting up permissions, make sure POC Admin can read and create the Users table. You can set up the permission so that they only see records from their own company 3. Create a custom button that would autofill the company based on the user’s company: 4. In the Create form, hide the company field so the POC Admin can’t change it The POC admin should now be able to create new users for their own company. The new user should then be able to register themselves on the next data sync, probably in 15 or so minutes. I realize this is a lot of work for what seems a simple task, and we will definitely look into making permissions easier and more robust.
l
Please also consider allowing a user to be assigned to multiple roles and to be able to specify multiple roles that are able to access any given layout. I think you were on the right track with the short-lived release a while back of a new method for defining roles and permissions but that roll-out was retracted. What happened?
e
Hey @loud-magazine-63930 I appreciate your honest feedback. We definitely want to allow multiple roles in the future. I believe the roles and permissions model you’re mentioning is live for any new workspace, while the migration of older ones is a trickier affair that needs a bit of manual work. We’re working on automating this migration process. 🙂
c
@elegant-eve-85294 thank you!
👍 1