Clients

Each client is a TechWatchAlert organisation attached to your partner organisation. It keeps its projects, stack and alerts, kept apart from those of your other clients; your team gets in without an invitation, and you choose its plan, Team or Pro, paid for through your Partner subscription.

• Who it is for: owners and administrators of the partner organisation.
• Where: Partner space › Clients; a click on a client opens its client page.
• Prerequisite: the Partner plan must be active to add, attach or change a client’s plan (see Partner plan inactive).

The client list

1. Add a client (see below).
2. Search a client: filters the list as you type, ignoring case and accents.
3. Export as CSV: downloads the rows shown (clients.csv, “;” separator, readable by Excel).
4. Name of the client, its number of projects and “NIS2” if the module is enabled on one of them. A click on the row opens the client page.
5. Status (see Statuses).
6. Plan: Team or Pro.
7. Exploited and Critical: alerts still open whose CVE is exploited, or critical (a coloured dot shows there are some).
8. Alerts 30 d and Last alert.

Order: the most exposed client first (most open exploited, then critical, then alerts over 30 days), then by name. The counters only cover projects you are a member of. On a narrow screen, the number columns are hidden.

Statuses

Status	Rule applied
To set up	The client has no project, or no component in its projects’ stack.
Invitation pending	Project and stack are there; a contact invitation is awaiting an answer, and none of the client’s contacts is a member yet.
Active	Every other case.

Only named, unexpired invitations count. The partner’s team, present at the client’s by delegation, is not a “client contact”.

The client page

1. Clients: back to the list.
2. Status and the client’s start date (“Client since …”).
3. Open the client’s space: opens its default project on its dashboard. Greyed out while the client has no project.
4. Properties: plan, owner, and the Exploited, Critical, Alerts 30 d and Last alert indicators (across all the client’s projects).
5. Plan: Team or Pro, which you can change at any time.
6. The client’s Projects.
7. Create a project at the client’s.
8. The client’s Contacts.
9. Invite a contact.
10. Detach the client.

The client’s plan

A plan change applies straight away and billing follows. Switching to Team a client that has NIS2 enabled asks for confirmation: Team does not include NIS2, so the module will be locked for this client; its NIS2 data is kept and returns with Pro.

Owner

The Owner row shows the address of the client’s owner, or “Your team (no owner on the client’s side)” for a client created from the Partner space: your organisation’s owners stand in until the client has an owner of its own.

Getting started

While a step is missing, the Getting started section lists the three steps and their progress:

Step	Done when	Action offered
Create a project	the client has at least one project	Create
Fill in the stack	at least one component is in the stack of one of its projects	Open the stack (default project; not shown without a project)
Invite a client contact	a contact is a member, or an invitation is pending	Invite

Projects

The table gives, for each project, its name (“default”, “NIS2” pill), the number of Components in its stack and its Open alerts. A click opens the project at the client’s, on its dashboard.

Create a project opens a window: the name (100 characters at most) and, for a client on Pro, the Enable NIS2 for this project box (on Team: “NIS2 is included in the Pro plan.”). The project is created in the client’s organisation, within its plan’s quota; your team has access straight away.

Contacts

The list gathers the client’s members (not your team) and pending invitations, with their profile: Read-only, Management, or “Custom access” for access set by hand. The owner has the Owner pill; an invitation, the Invitation pending pill and its date.

Inviting a contact

The client’s contacts use TechWatchAlert like any member: they are members of the client’s organisation, never of yours.

1. Title: the contact will receive an email in your name and will only access this client.
2. Contact’s email address.
3. Read-only profile (default).
4. Management profile.
5. Send the invitation.

1. On the client page, click Invite a contact (or Invite in Getting started).

2. Enter the email address and choose the profile.

3. Click Send the invitation. The window confirms it was sent and shows the invitation link, to copy and pass on another way. Invite someone else clears the form; Done closes the window.

   

Profile	Role in the client’s organisation	Role on its projects	What the contact can do
Read-only	Member	Viewer	See alerts, CVEs and reports for every project, without changing anything.
Management	Administrator	Administrator	Also manage the stack, cases and members of their organisation.

Useful rules:

• each profile is carried by a group of the client’s organisation, “Client · lecture seule” or “Client · gestion”, created at the first invitation; it gives access to all its projects, present and future, and the client’s administrators can change it;
• the invitation is valid for 7 days; the contact creates their account from the link if they have none;
• the invitation goes through the usual flow: a second invitation to the same address is refused while the first is pending, and the contact takes a member seat at the client’s, within its plan’s limit.

The contact receives an email naming your organisation, the one they know, the access granted and the expiry date:

Adding a client

Add a client (dashboard, client list or context selector) opens a window with two tabs: New client and Attach.

New client, in three steps

1. Title and progress (“Step 1 of 3”).
2. New client and Attach tabs.
3. Client name (100 characters at most).
4. Plan: Team or Pro, with the monthly price of the tier reached.
5. Next (on the last step, Create client).

1. The client: its name and plan.

2. First project: its name (“Main” by default) and, on Pro, the Enable NIS2 box.

   

3. Contact (optional): a contact’s email address and access, Read-only or Management. Leave it empty to invite them later.

   

4. Click Create client. The organisation, its default project and the invitation are created together; a message confirms it and the client page opens, with its getting-started steps.

Back returns to the previous step without losing anything. A client created this way has no owner of its own: your organisation’s owners stand in until you make one of its contacts the owner.

Attaching an existing organisation

The Attach tab entrusts your partner organisation with an organisation that already exists, along with its projects, stack and history.

1. Attach tab.
2. Plan of the client once attached.
3. Organisations you own: those that cannot be attached are greyed out, with the reason (“Your partner organisation”, “Already your client”, “Already a client of partner”, “Personal space: cannot be attached”).
4. Someone else’s organisation: the attachment link, once created, with its expiry date.
5. Attach: attaches the chosen organisation.

You own it: choose the organisation, then Attach. An organisation that pays for its own subscription must cancel it first; otherwise attaching is refused with that message and the organisation is greyed out from then on.

You do not own it: choose the plan, then Create a link (plan) and send the link shown to its owner (copy button). The link is valid for 7 days, can be used only once and carries the chosen plan.

The attachment link, on the owner’s side

The owner opens the link (after signing in if needed) and lands on this page:

1. Who offers to manage the organisation (partner’s logo and name).
2. Plan (“plan, paid by the partner”) and expiry date.
3. Effects of attaching.
4. Organisation to entrust: the organisations they own; those that cannot be entrusted are greyed out with the reason (already managed by a partner, partner organisation, own subscription to cancel first, personal space).
5. Accept: attaches the chosen organisation; the page confirms “Organisation attached”.
6. Later: back to the dashboard without doing anything.

The same rules apply as for direct attaching. The client appears in your list straight away. An unknown, expired or already used link shows “Invalid attachment link”, with the reason.

Making an owner and detaching

Detaching a client makes it independent: your team loses access, the client keeps its data and returns to its own plan, and it is no longer billed on your subscription. This is only possible if the client has its own owner; otherwise it would be left without one.

The client has its own owner (attached organisation, or an owner you designated): the Detach the client section offers the Detach button, which asks for confirmation. The client disappears from your list.

The client has no owner of its own: the section offers to designate one among its member contacts (who have an account), with Choose a contact then Make owner. The same button appears on each member contact’s row. If no contact has an account yet, the section suggests inviting one.

Make owner makes the contact the owner of the client’s organisation: they join the Administrateurs group (all rights on all projects) and receive a notification. Your team stays administrator and keeps access. The client can then be detached. Only a client contact can become owner, never a member of your team.

Your team’s access to clients

• Who: the owners and administrators of your partner organisation; a plain member does not have this access.
• Which rights: at each client’s, administrator access (owner for your owners while the client has no owner of its own), and a system group “Partenaire · your organisation” that opens all projects, present and future, as administrator.
• Always up to date: access follows your team whenever a client is added or leaves, whenever your team changes, and every night. A technician added as administrator sees all your clients straight away; if they leave, they lose access everywhere.
• On the client’s side: in the client’s members, these accesses carry the “Partner · your organisation” label; they take no seat and the client cannot remove them.

To add a technician, see Team.

Who can do what

Action	Partner owner	Partner administrator	Partner member	Client contact
See the client list and client pages	Yes	Yes	No	No
Add or attach a client, create a link	Yes (plan active)	Yes (plan active)	No	No
Attach an organisation directly	If they own it	If they own it	No	No
Change a client’s plan, create a project for it	Yes (plan active)	Yes (plan active)	No	No
Invite a contact, make an owner, detach	Yes	Yes	No	No
Accept an attachment link	—	—	—	The organisation’s owner

FAQ

The Detach button does not appear. The client has no owner of its own. Invite a contact, wait for them to accept, make them the owner, then detach.

Open the client’s space is greyed out. The client has no project yet: create one from its client page.

What happens to a detached client? It keeps all its data and returns to its own plan; your team no longer has access.

Partner spaceAccess, dashboard, selector, client banner.

Alerts and reportsThe alert queue of all clients and the PDF summary.

Team, billing and brandingTechnicians, Partner subscription, logo.

Team, roles and groupsAn organisation's roles and groups.