You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are working with an Activity Report and consuming the Catalog - Permission table to analyze user permissions in our system. However, we noticed that the table does not contain any Date field that indicates the duration for which a user has a specific permission.
For example:
User ABC is displayed as an Admin for a Test workspace in the activity report.
Recently, we removed ABC from the workspace, but the report still shows them as an Admin for the Test workspace.
This raises concerns about the accuracy of permission tracking and makes it difficult to determine the historical state of permissions for a specific period.
Problem Analysis
Lack of Time Dimension in the Permission Table
The table seems to only store the current state of permissions without tracking changes over time.
If permissions are updated, the system may override old values instead of maintaining a history or keeping track using a Date field.
The text was updated successfully, but these errors were encountered:
We are working with an Activity Report and consuming the Catalog - Permission table to analyze user permissions in our system. However, we noticed that the table does not contain any Date field that indicates the duration for which a user has a specific permission.
For example:
User ABC is displayed as an Admin for a Test workspace in the activity report.
Recently, we removed ABC from the workspace, but the report still shows them as an Admin for the Test workspace.
This raises concerns about the accuracy of permission tracking and makes it difficult to determine the historical state of permissions for a specific period.
Problem Analysis
Lack of Time Dimension in the Permission Table
The table seems to only store the current state of permissions without tracking changes over time.
If permissions are updated, the system may override old values instead of maintaining a history or keeping track using a Date field.
The text was updated successfully, but these errors were encountered: