Skip to content

projectEureka has two layers of roles.

  • System roles apply to the whole environment: a user, a user allowed to create projects (Project create, set by an admin in User Administration), and a System admin.
  • Project roles apply in one project: Owner, Editor, or Reader. The project Owner sets them under Members in Project Settings. See Add and manage members.
Action Reader Editor Owner System admin
See the project and use what is shared ✓ ✓ ✓ ✓
Launch an app from an existing launcher ✓ ✓ ✓ ✓
Delete an app session you started ✓ ✓ ✓ ✓
Pause, resume, or restart your own session ✓ ✓ ✓ ✓
Watch a shared desktop ✓ ✓ ✓ ✓
Request control of a shared desktop ✓ ✓ ✓
Force-take control of a shared desktop ✓ ✓
Pause, resume, or restart anyone’s session in the project ✓ ✓
Submit a saved flow, and stop your own run ✓ ✓ ✓ ✓
Stop anyone’s run in the project ✓ ✓
Create or change files in a project or home folder in Storage ✓ ✓ ✓ ✓
Create, read, or delete objects in a managed or keyed external bucket in Storage ✓ ✓ ✓ ✓
Add, change, or remove launchers and flows ✓ ✓ ✓
Add, change, or remove buckets in Storage Settings ✓ ✓ ✓
Pick a credential for a flow stage ✓ ✓ ✓
Add or remove project credentials ✓ ✓
Change project settings and members ✓ ✓
Turn on Project login (the project user) ✓ ✓
See all project jobs on Jobs ✓ ✓
Delete a flow ✓ ✓
Archive, restore, or delete the project ✓ ✓
Raise the project’s Max run time ✓
Use the administration pages ✓

A Reader can launch an app from an existing launcher and delete an app session they started. They cannot delete someone else’s session. A system admin can manage a project’s buckets in Storage Settings without a project role. A Reader can write files in a project folder, run a saved flow, and write, read, and delete objects in a managed bucket or a keyed external bucket. The key helper does that object work and does not return the key. A public bucket with no key stays read only. A Reader cannot add, change, or remove the bucket entry. The server refuses eureka bucket add and eureka flow import with a plain message saying a Reader cannot do that. That holds for the page, the command, and a bucket request submitted as a run.

  • Any project member can launch an app or submit a flow with no access to the environment’s provider settings. Provider connection details (cloud keys, SSH keys, kubeconfig, environment variables) are readable by system admins only. Members see the image names and instance-type hints they need to launch.
  • Passwords and keys that you save, such as a bucket Key, are write-only for everyone except system admins.
  • A session’s desktop password is visible to members of that session’s project and to system admins.
  • A person sees their own project list and the people in their projects. A system admin or auditor sees everything.
  • An auditor can read and query but cannot change anything.

No role signs in as the project user. Only a shared desktop runs as it.

To create a project you need Project create, which an admin turns on for you. You become the new project’s Owner.

Projects · Add and manage members · Manage users