Saltar al contenido principal

Projects and Team

A project is the container for everything you build: one plugin, one sandbox, and the people allowed to work on them.

One project, one plugin

A project holds exactly one plugin. If you are building two integrations, create two projects. The portal will not offer a second plugin on a project that already has one — it shows Manage plugin instead.


The projects list​

Projects lists everything you are a member of, not just what you created. From here you create a new project; from a project's card you open it.

Inside a project​

The project page has three parts:

The header — the project's name (in monospace, because it is an identifier you will type) and its description. Owners and admins can edit both.

Plugin — a compact card showing the plugin's current lifecycle state. If the project has no plugin yet, this is where you create it. The card also carries the one short action worth taking from here: Submit for review, or Resubmit when a reviewer has sent it back. Everything deeper lives on the plugin's own page — see Building your plugin.

Sandbox — status and an Open sandbox link. It is a pointer, not a control panel; the sandbox itself has its own screen. If none has been provisioned, the card says so.


Roles​

Every member holds one of four roles. The portal hides controls your role cannot use, but the server is the authority — it enforces these rules regardless of what the UI shows.

Can…OwnerAdminMemberViewer
View the project✅✅✅✅
Rename / re-describe it✅✅——
Create the project's plugin✅✅——
Add, re-role and remove members✅✅——
Grant the owner role✅———
Archive the project✅———

Two consequences worth knowing:

  • An admin can invite people, but cannot make anyone an owner. An admin hands out admin, member or viewer; only an owner can hand out owner.
  • Archiving is owner-only. It is the one action an admin cannot reach.
Creating the plugin is an owner/admin action

If the plugin card says "An owner or admin can create one from this project", your role is member or viewer. Ask an owner or admin to either create the plugin or raise your role.


Inviting your team​

Adding members, changing roles and removing people are all done from the project. The mechanics of the invitation itself — what the invitee receives and how they accept — are covered in Developer Account.


Next​

With a project in place, build its plugin.