Collaboration
ORQO is a multi-user platform. An organization can have many members, each with their own projects, workflows, and credentials -- and a structured way to share those with teammates.
This guide explains the mental model. If you've ever wondered "who can see my work?", "how do I let a teammate run my workflow without showing them how it works?", or "what happens when someone leaves the org?" -- start here.
Two questions, two answers
Collaboration in ORQO is shaped by two independent questions:
1. What can you do in the org? That's your role: member, admin, or owner. Role decides whether you can install Apps, manage members, change billing, and so on.
2. Who can see your work? That's visibility: every project, workflow, and trigger you create is private by default. You decide when to share, with whom, and in what mode.
These two axes don't bleed into each other. An admin can see another member's project (audit-view), but they cannot edit it. Only the creator can edit.
The visibility tiers
Every project, workflow, and trigger has one of three visibility tiers:
| Tier | Who can see it |
|---|---|
| Private | Just you, the creator |
| Shared | You + specific members you've invited |
| Org | Every member of the organization (read-only) |
Sharing is opt-in. Nothing leaves your private space until you share it.
Two ways to hand off a workflow
When you want a teammate to use a workflow you built, there are two distinct mental models. Picking the right one matters:
Delegation -- "Run my workflow, on my credentials, from my project."
You share the workflow directly. The recipient can hit the Run button; the workflow runs as if you ran it (your credentials, your project). This is great for ad-hoc help and for non-technical teammates.
Template -- "Here's the recipe; build your own copy."
You export the workflow as a template. Anyone in the org can install it into their own project, where it runs on their credentials. This is great for reusable playbooks.
See Sharing a Workflow and Templates and the Org Marketplace for the full picture.
What's in this section
| Page | Read it when |
|---|---|
| Roles: Member, Admin, Owner | You're figuring out who can do what at the org level |
| Visibility and Sharing | You want to share a project, workflow, or trigger |
| Sharing a Workflow | You want a teammate to run your workflow -- in Inspector or Runner mode |
| Templates and the Org Marketplace | You want to ship a reusable workflow recipe |
| Removing a Member | Someone is leaving the org and you need to transfer their work |
| Activity Feed | You want to see who shared, installed, or changed what |
Learn more
- Reference: Projects -- visibility scopes and policy
- Reference: Workflows -- run access and sharing semantics