-
-
Notifications
You must be signed in to change notification settings - Fork 213
Description
@arbokrad asked on SFXD about giving non-admins the ability to make some edits to logging data:
nebula question for you - if we want to have some users able to modify logs (like, mark them resolved) but not manage any of the other nebula settings... is there a good fit from the existing permissions? or should we be looking at using LoggerLogViewer and a new permset to grant write access to the Log__c object and fields?
we have a admin-esque user going through and resolving things that come up, but that person should definitely not be able to change log levels or retention duration or anything of those sorts
Currently, the LoggerEndUser permission set only has read access to objects/fields - but it was originally intended to handle situations like above, where users can make some minimal edits to fields, manage tags (by creating/deleting LogEntryTag__c records), etc. - but at some point over the years, the permission set changed to only having read access 😢
To handle these situations, the LoggerEndUser should be updated to have CRUD access in a few places:
- Edit access on
Log__cobject + certain fields, likeLog__c.Comments__c - Created/edit/delete access on
LogEntryTag__c - Maaaaaybe create access on
LoggerTag__candLoggerScenario__ctoo - I need to think about this one some more before deciding