Permissions For Objects
J
Jeff Valin
At minimum, role permissions so certain objects can be restricted to admin.
Ideally, user permissions to control object visibility by user.
Log In
W
Wesley Schiesari
This is very important, today the created objects keep appearing to all users, and there's no point in this, it's enough to create just one permission to limit visibility and editing for users.
R
Ruth Fontal
I think this is a fundamental issue, and it became clear two years ago. What progress has been made on this front? Will this ever be implemented?
O
Orney Martinez
Any progress on this guys ? we really need this feature on our field (Insurance), I'm pretty sure in others as well.
U
Upasana Rai
Any progress on this?
A
Aayush Singhal
Merged in a post:
Customize User Permissions for Custom objects
J
Joe LaMothe
Currently you can change user permissions for all standard menu items. It would be nice for custom objects if we could also customize view or manage permissions for them while they are being created.
G
G J
Object-level access control is a must. It'll be super nice to be able to specify who can read/write/change record-level information for objects both individually and globally.
Pallavi Kothari, Siddharth C, Aryan Goyal & Sales & Marketing: for your action.
P
Pallavi Kothari
G J: Thanks for flagging. This is noted.
K
Keith Besherse
Sales & Marketing Core Platform RevEx Group Shivam HighLevel Chase Buckner, granular permissions should not be a separate request for each feature. It should be a prerequisite for release from Labs. It is fine if you want to Beta test and offer in Labs without agency and sub-account owner ability to constrain their admins and users. But before releasing to the common subaccount admin the specific restrictions should be applied so non-tech business users don't change base settings without agency admin &/o subaccount owner approval. Thank you!
Ideas Board Finds: Granular Admin/User Permissions for each feature/product.
No product, feature, or upgrade should be released out of Beta/Labs to the general user base without granular permissions as a design criteria. Each feature should have specific user permissions.
Search: More Granular & Permissions
These are only a few of the many examples:
M
Muhammad Jahangir
yes please
L
Leonardo Leitão
It's essential for us. We work with medical clinics and some information should be visible only to doctors, not to secretaries or assistants. Allow us to use permission settings to define who can see specific custom objects (entire categories) or individual fields. This feature is very important.
R
Rosebell Bicar
Core Platform OMG, look at the trend. This issue is everywhere. Are you guys going to do something about it?
A
Abbas Mebrouki
Yes, this is very important to have permissions for the custom objects, similar to the permission we have for Opportunities, Contacts, etc.
Load More
→