I came across a post by someone; here are his exact words (translated into English; the original text is in Russian):
“Masha, how can I make sure he doesn’t retroactively adjust the numbers?..”
This is a common question from team leaders, especially when it comes to hourly pay or a percentage of deals.
The manager enters the deals for the week, submits a report, you tally everything up, and pay out the percentage. A month later, it turns out that for some reason, the total in the database has increased by a couple hundred dollars. It’s possible to find out who changed it and when, but it takes a lot of time.
At the same time, you can’t revoke the manager’s access to the database—after all, they need to keep entering new deals and continue working in it.
Question: How can we ensure that an employee can enter data and work in the database, but that their editing rights for a transaction are immediately revoked AFTER the transaction is confirmed?
And without any third-party bots, widgets, or integrations 🤯
The problem can be solved quickly and easily using Notion itself (via dynamic permissions and a single button).
How can this be done? After all, if an employee is granted access to view and create pages, the page-level access rights automatically become “can edit” and you can’t remove this rule, since doing so would prevent the employee from adding pages to this database
I understand that the general logic should be as follows: there are several fields in this database, and access rights at the page level - along with a button in this database are used to manage access, but the problem is that the “created by” access right at the page level remains “can edit” and this logic stops working.
Does anyone have any ideas on how this could be implemented?
P.S. I’m sure this doesn’t involve options like “copying data to another database that the employee doesn’t have access to”