Is it possible to limit visibility and access to cycles by user?
The cycle table has an important access control setting for cycles — cycle access type.
It operates depending on how the creator_id field is filled — this is a technical field in the cycle table, which by default is set to the user who creates the cycle.
This code can be modified to add other users.
Users specified in this field are cycle creators.
Access is set relative to the cycle creator:
Only own cycles are visible.
Other users' cycles are visible but cannot be opened.
Other users' cycles are visible with the ability to view their contents.
All cycles are available for editing.
Why doesn't restricting access by prefilters in the cycles table fully restrict access?
Because the prefilter filters rows in the cycle tables. It does not manage access rights to the tables within the cycle.
Can I assign access to multiple users?
Yes. Users can be added to creator_id programmatically.
Can I specify a user who gets full access to the cycles of another user?
Looking ahead, it can be said that in the user table, any user can be granted access to another user's cycles as if they were also the creator.
This is managed by the field user cycle access.
Can the visibility of tables within a cycle be separated by role?
Yes. Access to cycles does not imply access to all tables within the cycle. If a user’s role does not have access to a particular table within the cycle, they will not see it.