Tie Permissions to Status
in progress
Marianna Buldo
marked this post as
in progress
Isaac Gutierrez
Merged in a post:
Set record permission by status with automation
Z
Zaffre blue Parrot
I can see a need to automatically set record permission settings using an automation that is triggered by a status change. For example, when a job estimate has been sent out and the estimate status is set to "finished", it would be good if the record permissions for those records were set by an automation so only a special admin can edit them. This would prevent accidental or intentional changes to the estimate. In particular I see this as a way to preserve the integrity of the estimate line items so they can be archived as a history of how the estimate was assembled and as a resource for future estimates.
Jon Darbyshire
Great to hear your perspective, Zaffre blue Parrot! I have a few more questions for you:
- Can you provide more details on the 'special admin' role? What specific permissions should they have?
- Are there any other status changes that should trigger a change in record permissions?
- Should there be a way to manually override these automated permission changes, and if so, who should have that ability?
Z
Zaffre blue Parrot
Jon Darbyshire
Z
Zaffre blue Parrot
Also I thought of another scenario where automatic locking could be important. Assume CostTable has a record 007 and there is one record in LineItemsTable that is linked to the CostTable record 007. If the cost in CostTable rec 007 changes the effect will only be seen in that one record in the LineItemTable it is linked to. But lets say there is a really good reason to let more that one record in LinItemsTable link to rec 007 in CostTable... now if the cost changes it will affect two records in the lineItem table... This would be a problem if each of the LineItems linked to 007 was part of two different project estimates. So I could see where if there was a process that noticed multi-links to a single record, then the Cost Field in that recored could lock from changing. So you ask - why would anyone ever want to do something like that... Well the advantage of using smartsuite for project estimating is to capture all of the data that is created across all project estimates... This lends itself to a very quick and dirty method of estimating that is to use a historic cost applied to a new estimate. If the situation later demands a different number then at that point a new record in the CostTable can be created.... just a thought
Z
Zaffre blue Parrot
Noticed that there is another thread talking about this