Add project

Add a separated project to your PMT account.

Use this when another customer, site, branch or operational group should remain separated under an existing account.

Existing account required. New to PMT? Start with one result →

You will need

Account reference
The reference from the existing account.

Primary signup email
It must match the account.

A reason for separation
Customer, site, branch or another distinct operational group.

Add project

Use this form only to add a separated project to an existing PMT account.

Add a PMT project
Create another separated project under an existing PMT account. Use project-specific credentials so future signals land in the right place.
Fields marked * are required.
Account
Use the account reference shown when the account was created.
Must match the primary signup email used for the existing account.
Project details
Used to help recognise the project. Keep it clear and non-sensitive.
Must be unique within the account. Use a simple reference that helps separate customers, sites or groups.
Avoid sensitive data. Notes should help with project setup, not describe private system details.
This form creates another project. It does not install anything, start checks, change billing automatically, or create broad coverage.

Before submitting

  • Use this only for an existing PMT account.
  • Use the account reference from the original signup.
  • Use the primary signup email for that account.
  • Keep project names and refs clear but non-sensitive.

The form does not install anything, discover systems or start ongoing visibility by itself.

New account?

Do not use this form for a first PMT account.

Start with one result instead.

When to create another project

Create another project when separation has a real purpose:

  • another customer
  • another site or branch
  • another operational group
  • another internal project
  • a signal set that should not be mixed with another project

Do not create projects merely to imitate a full estate model.

Keep the boundary useful.

Project name is optional and should help recognition without carrying sensitive information.

Client ref is optional and, when used, must be unique within the account.

Separate at source where that boundary matters. Selected project views can still be combined in the webapp where useful.