Skip to content
Book a demo

Overview

Ren organizes work in four levels. Each level sits inside the one above it.

  • Organization: your company or account. It holds members, billing, and settings that apply everywhere.
  • Space: a team or client inside the organization. It decides who can see the work, and it runs on its own machine.
  • Project: one kind of work inside a space, such as code review. It sets the instructions, tools, and storage Ren uses for that work.
  • Chat: one request to Ren inside a project, and everything Ren did to answer it.
Organization
Northwind
Space
Engineering
Project
Code review
Chats
  • Review the login fix
  • Review the new API

Each organization starts with a General space for all members. Each member gets a private Personal space. Add spaces for teams or clients.

Example: a company’s internal agents

Northwind’s engineers share the Engineering space in their company’s organization.

Engineering has two projects:

  • Code review, with the team’s repositories and review instructions.
  • Incident triage, with access to the on-call tools and a runbook skill.

Code review uses separate chats for the login fix and the new API, and both share the project’s repositories and review instructions. Incident triage uses a separate project because it needs different tools and instructions.

Example: an agency serving clients

Brightline is a marketing agency. Its organization is Brightline, with one space per client, like Acme.

The Acme space has two projects:

  • Campaign reporting, connected to Acme’s ad accounts.
  • Content production, with Acme’s brand guidelines and assets.

Campaign reporting uses separate chats for weekly reports and campaign comparisons. Only Acme’s team joins the Acme space. Acme’s tool accounts use space credentials, and another client’s space can’t access Acme’s work or credentials.

What else you configure

Most features attach to a project or a space.

Blueprints add a ready-made project or space to your organization.