Closed inghamn closed 5 years ago
Yes on the permissions. They are no longer Engineering, Paul is transportation and Eric is planning. We call their job role address coordinators. Perhaps a role called cityaddress or cityaddressedit.
Here are the permissions we can now grant in Master Address:
And then these things all have just a generic "update" action:
For roles called "cityaddress" and "cityaddressedit", do we want to grant permission for all of these - or just some of them?
They should be granted permissions for all of them. We need just one role.
If we're granting permission for all these things, do we need another role? We already have the "GIS" role which has permission for all of these things.
Is this just a role within the master address app or within postgres? GIS People will have permissions to do things with data in other postgres databases that we don't want Eric and Paul to do. True there isn't a way for them to easily get there now.
This is just about the roles in the web interface for Master Address.
OK. Then they should have the same permissions. The role name GIS isn't really accurate. but you can use it if you want. Not all GIS staff will necessarily have permissions to this.
We can rename the role to whatever you think makes sense. Would something like "City Staff" or "Employee" make more sense?
I think that something like addressedit or cityaddressedit would be better. Not all employees or city staff should have editing rights.
Okay, I will:
We launched with Engineering users having the same permissions as the general public. We should add in some permissions for them.
The old Master Address granted full permissions (do anything with)
Do we just want to replicate these permissions in the new version?