Orviqa

Orviqa for teams

A team workspace is one place where several people work on the same open-source projects: the analyses, the plan, the drafts and the record of what happened are shared, and the decisions that speak for the project in public stay with the people you choose. It suits a company that maintains open-source projects, a developer relations team, or a group of maintainers who promote a project together.

What the team shares

Everything a personal workspace has, held once for everyone: the repositories you track, each analysis and the tasks it found, the 30-day plan, drafts and campaigns, connected channels, and the outcomes you record. When one person finishes a task, everyone sees it done.

Each person chooses which of the workspace’s repositories they are working on, and switching does not move anyone else’s view. Two people can work on two projects in the same workspace at the same time.

Three roles

Most of the work is open to everyone, because it is the everyday work and the workspace pays for it by design. What is held back is anything that speaks for the project in public, changes what the workspace is connected to, or spends money. Each rule is checked on the server, so it holds even for someone calling the API directly.

RoleWhat they can do
MemberRun analyses and searches, draft posts, plans and campaigns, record outcomes, switch between the workspace’s repositories, and create a personal API key for a coding agent.
AdminEverything a member can, plus approving drafts and publishing them, adding repositories, connecting channels and analytics, publishing the project page, choosing whether the workspace shares data for cross-project learning, and managing members.
OwnerEverything an admin can, plus buying credit and opening the billing portal. Only an owner can make another owner.

Nothing is posted without an approved draft. A scheduled post is checked again before it goes out: still approved, and the channel still connected.

Invitations go to one person

Owners and admins invite by email, and nobody can invite someone above their own role. An invitation can be accepted only by an account whose verified email is the address invited, so a forwarded link does not let anyone else in. Each link works once and expires after seven days.

Credit belongs to the workspace

A team workspace starts empty and with no credit. Owners buy credit in packs of $100 or more, at the same per-token rate as personal packs, and everyone in the workspace draws on it. Joining a team adds no credit: the free tokens each person gets on sign-up stay in their personal workspace. The packs and the rate are on the pricing page.

Whose GitHub access it uses

When you run something yourself, Orviqa uses your own GitHub connection. Work that runs in the background for the workspace, such as daily readings and issue searches, uses an owner’s connection and never a member’s, because a member’s token can see whatever that person can see. What Orviqa does with GitHub access is set out on the security page.

Starting one

Sign in, open the workspace menu and choose “New team workspace”. Add a repository, then invite the people who will work on it. New to promoting an open-source project? The guide to promoting an open-source project is where the work starts.