We would like the ability to assign custom permissions to users on our team. We have technicians that we don't really need to give the "Manager" role as that comes with more power than they really need and they get more notifications than they really want. However, they need the ability to edit checklists which is a "Manager" and above permission. Being able to customize user permissions would solve this issue for us.
Feature Request: Custom Role Permissions
- Thread starter HDMSupport
- Start date
Hey there! Thanks for this, it's a great callout on permissions.
Quick follow-up so I can get this in front of the right folks. When you say Manager comes with more power than your technicians really need, what's the specific stuff you're thinking of? Managing other users, deleting projects or photos, something else entirely?
Sounds like checklist editing is the one thing you actually need unlocked for them, so knowing what you'd rather keep locked down helps paint the full picture. Appreciate you taking the time to write this up!
Quick follow-up so I can get this in front of the right folks. When you say Manager comes with more power than your technicians really need, what's the specific stuff you're thinking of? Managing other users, deleting projects or photos, something else entirely?
Sounds like checklist editing is the one thing you actually need unlocked for them, so knowing what you'd rather keep locked down helps paint the full picture. Appreciate you taking the time to write this up!
Upvote
0
So we started with having everyone as a Manager but now that we are using the proposals and invoicing systems in Company Cam more, the guys are getting notifications about proposal approval and payment submission sent to their personal emails and into their apps. One, this is more information than they need and two we would rather not have information about our payments going to emails out of our business email ecosystem. So we then stepped everyone outside of our project manager and office manager down to standard. Now the crew leads cannot manipulate checklists which makes certain documentation and work assignment workflows more complicated. So really we need two things that are semi-related:
1) We need to be able to control who gets notifications and emails about certain action items like proposal approvals and payments, especially payments. It is my understanding that all users with the Manager or Admin role get the notifications, along with any users that are assigned to the project with no way to change this notification setting anywhere that we have been able to find.
2) We want to be able to control permissions of those with standard permissions to be able to manipulate checklists. There may honestly be more permissions that are different between the roles but without a list of what permissions each role has, there really isn't any way for us to know until someone tries to do something and then they can't do it.
1) We need to be able to control who gets notifications and emails about certain action items like proposal approvals and payments, especially payments. It is my understanding that all users with the Manager or Admin role get the notifications, along with any users that are assigned to the project with no way to change this notification setting anywhere that we have been able to find.
2) We want to be able to control permissions of those with standard permissions to be able to manipulate checklists. There may honestly be more permissions that are different between the roles but without a list of what permissions each role has, there really isn't any way for us to know until someone tries to do something and then they can't do it.
Upvote
0
This is exactly the detail I was hoping for, thank you for laying it out so clearly!
A couple of things I can speak to directly:
On checklists: what you're running into matches how it works today. Admins and Managers can create, edit, delete, and duplicate checklists and fields, but Standard and Restricted users can only edit fields on checklists they personally created. So once you moved your crew leads down to Standard, that ability went with it. There's a full breakdown of what each role can and can't do here if it's helpful: https://help.companycam.com/en/articles/14010242-permission-roles-explained.
I hear you on wanting more granularity between "Standard" and "Manager minus notifications," and that's genuinely useful context for us as we think through where role permissions could flex more.
On notifications: this one's real too. Right now, proposal and payment notifications go out to anyone with Manager or Admin, plus whoever's assigned to the project, and there's no per-user control to turn that off. I don't want you exposing payment info outside your business email ecosystem any more than you do, so I've gotten this in front of the team that owns notifications.
No promises on timing for either one, but this is a really clear, well-reasoned writeup and it's the kind of thing that makes a difference when we're prioritizing what to fix next.
If you have additional thoughts after checking out that permission roles article, let me know. Thanks again for taking the time!
A couple of things I can speak to directly:
On checklists: what you're running into matches how it works today. Admins and Managers can create, edit, delete, and duplicate checklists and fields, but Standard and Restricted users can only edit fields on checklists they personally created. So once you moved your crew leads down to Standard, that ability went with it. There's a full breakdown of what each role can and can't do here if it's helpful: https://help.companycam.com/en/articles/14010242-permission-roles-explained.
I hear you on wanting more granularity between "Standard" and "Manager minus notifications," and that's genuinely useful context for us as we think through where role permissions could flex more.
On notifications: this one's real too. Right now, proposal and payment notifications go out to anyone with Manager or Admin, plus whoever's assigned to the project, and there's no per-user control to turn that off. I don't want you exposing payment info outside your business email ecosystem any more than you do, so I've gotten this in front of the team that owns notifications.
No promises on timing for either one, but this is a really clear, well-reasoned writeup and it's the kind of thing that makes a difference when we're prioritizing what to fix next.
If you have additional thoughts after checking out that permission roles article, let me know. Thanks again for taking the time!
Upvote
0