Register an existing project

Give work that already exists in Delegate or CDN one project identity in Beyond Projects, without a template, without development access and without changing anything in those products.

  • Availability: Experimental
  • Evidence: Recorded run
  • How-to guide

When to use this

Use it when the work is already there: a project your team runs in Delegate, or applications it already has in CDN. Registering creates the one identity that represents that work, so that every product can refer to the same project.

It is not a way to start new development. For that, create a project from the template.

Before you start

  • You must be Owner or Administrator of the organization shown in the header. Register an existing project is absent for a Developer and a Viewer.
  • You do not need Workspace development access.

Register it

  1. In Projects, choose Register an existing project.
  2. The dialog explains what will happen: "Use this for work that already exists in Delegate or CDN. It gives that work one project identity. Nothing is created from a template and nothing in those products changes; link their records from each product afterwards."
  3. Fill in Project name and choose Register project.

Expected outcome: the project opens and the screen says "The project was created." Where a project created from a template shows its template under Created from, this one says "Adopted from an existing product record".

What it does, and what it does not

It does It does not
Creates a project identity in the organization Create anything from a template
Lets each product link its own records to that identity Find or match your existing records. Nothing is ever matched by name
Change, move or copy anything in Delegate or CDN
Open a development environment, or give anyone development access
Import an external repository. That does not exist

Registering is the first half. The second half happens in each product, under that product's own permissions:

  • In a Delegate installation that is connected to Beyond Projects, a workspace administrator attaches the existing Delegate project to the identity. See Adopt an existing Delegate project. Copy the project identity first.
  • In CDN, someone who can manage applications opens the project's applications and uses Add an existing application. See Add an existing application. The application keeps its identifier, releases, domains and addresses.
  • When records are linked, the product's entry on the project says how many, as in "2 linked here".

One product record belongs to one Beyond project. If a record is already linked to another project, the second link is refused and nothing changes.

Next action

Use Delegate with a Beyond project, or add the applications of the project in CDN.