In Sibe, there are two types of project permissions: Owner and Member. When you invite someone, they become a Member. That means they can comment, share the project, and upload new versions. The Owner of the team has all the Member permissions plus the ability to delete the project or scenes in it.
As the Owner of a project, you can give that role to anyone else, so they get the same permissions as you. But later, you can take that role back. You can't take the Owner role away from yourself.
Sibe offers two distinct access modes on the Project level:
Let's say you're the manager of a workspace called "Design Studio" and you have two projects: a public one called "Jewelry" and a private one called "Robotics". If the "Jewelry" project is public, everyone in the "Robotics" team can see its models. But if the "Robotics" project is private, the "Jewelry" team can't see any models in it.
In the screenshot, you can see that public mode is selected. That means anyone with access to your workspace can see this project.
In the project list, the current status of a project is indicated by a little icon next to its name.
The project was Public → now it is Private
Whoever had access to a public project or scene as a result of being inherited, will lose that access to the private project or scene directly.
The project was Private → now it is Public:
Whoever has direct access to a private project/scene will continue to have access after the project/scene is made public. All users who should have access because of inheritance will get access once the private thing becomes public.