Roles and governance

Everything your team already did with Ryno stays open to every member: reading the company catalog, attaching a project, publishing it and regenerating its token. Only a few rare gestures belong to administrators, and this page says which ones, who the first administrator is, where those gestures happen and where you can read what was done.

Two roles

Every person in your company workspace has one of two roles: Administrator or Member. There is no third role, and you cannot build your own.

An administrator can do everything a member can, and a few things more. The table lists what each role can do.

What you can do	Administrator	Member
Read the company catalog	Yes	Yes
Attach a project	Yes	Yes
Publish a project	Yes	Yes
Regenerate a project’s token	Yes	Yes
Remove a project from the workspace	Yes	No
Manage members	Yes	No
Appoint or remove an administrator	Yes	No
Remove someone’s access	Yes	No

If you are a member and you try one of the gestures reserved to administrators, Ryno tells you that only administrators of your company can do it, and nothing changes.

Who is an administrator at the start

The person who set your company up is its first administrator. If that person is no longer part of the company, the longest-standing member takes the role. For a company that is being set up now, it is the person setting it up.

Appoint an administrator

An administrator names another one from Members in the web application. Open the actions of a person’s row and choose Make administrator. To take the role back, choose Remove administrator role on the same row: the person stays a member.

Your company workspace is never left without one. When a gesture would remove the last administrator, Ryno refuses and says:

Your company workspace always needs at least one administrator.

Appoint someone else first, then remove the role.

Where these gestures happen

Gestures reserved to administrators happen in the web application, and only there. The desktop application has none of them: it shows each person their own role, and an administrator sees a Manage members link that opens the members page in the web application.

Where to read what was done

The Activity page of the web application keeps a line for each gesture an administrator makes: who did it, to whom or to which project, and when. It covers removing a project from the workspace, removing or restoring a person’s access, and appointing or removing an administrator. Regenerating a project’s token is logged too, whoever does it. Only administrators can read it.

A line stays for 365 days, then it is removed. Past that, the page no longer shows it.

Your plan decides how far back the page reads: the last 90 days on Team, the last 365 days on Business. The page says which, and on Team it offers Business to read further. Moving to Business shows the older lines again, since they were kept.

On Business, Export downloads the activity as CSV or JSON, with the filters you chose or everything from the last 365 days. Before anything leaves, it says how many entries match, and that the export is recorded: each export is a line of the activity too.