Request a customer workspace

Ask Quint to build a managed workspace for one of your customers: what you send, what is checked, and what happens next.

A new customer workspace starts with a request from the partner console. Quint reviews every request before anything is built. At the end of this page your request is submitted and you know what the customer will receive. Submitting needs the Analyst or Admin role.

1. Open Request customer

   In the partner console, open Request customer. The page says what it does: “Opens a managed-tenant request under your partner account. A Quint operator reviews every request before anything is provisioned.”

2. Describe the workspace

   Field	What to enter
   Customer name	The name shown on your board and in the customer’s dashboard.
   Slug	”Lower-case letters, digits and hyphens; becomes the tenant id and cannot be changed.”
   Region	One of your allowed regions. If none is listed, ask Quint to set one before requesting.
   Plan tier	Core, Team or Enterprise.
   Sector	Private sector, Financial services, Health, Telecommunications, Government, Critical national infrastructure or Other.
   Developer machines and Servers	How many machines to reserve from your quota. Enter at least one in total.

3. Name the customer of record

   Legal name, Contact name, Contact e-mail and an optional DPO e-mail. The contact is seated as the workspace’s pending owner and is the person Quint notifies about partner access. The partner is never the owner.

4. Add the references

   Contract reference: “The signed contract number between you and this customer.” Sub-processor acceptance reference: the reference under which the customer accepted Quint as a sub-processor. This acceptance is the legal basis for every later read-only session, so Quint checks it before building anything.

5. Submit

   Add Notes for the reviewing Quint operator if useful, then Submit request. Quint checks your partner standing, licence, region, capacity, quota and the references. A request that fails a check is refused with the reason and nothing is built.

​

After you submit

The request appears under Requests this session with the status “Awaiting Quint approval”. A Quint approver decides; a partner operator cannot approve, and neither can the Quint person who created a request. Once approved, the workspace is built the same way as any Quint workspace, then appears on your Managed customers board after its first posture snapshot.

The customer’s contact receives an invitation to claim the owner seat. It does not expire while the workspace has no owner.

​

What is different about a managed workspace

Three things are recorded that a workspace Quint sells directly does not have:

1. Who manages it: your partner account, on the workspace’s record.
2. Standing read-only access from the customer to you, carrying the contract and sub-processor references as evidence. The customer, or Quint, can revoke it at any time.
3. An unclaimed owner seat for the customer contact.

Everything else is identical. The customer’s data, your data and Quint’s data are kept apart.

​

If this fails

What you see	What it means	What to do
”Submitting requires the analyst role; yours is viewer”	Your role is Viewer	Ask a partner Admin to change your role.
”This partner has no allowed region. Ask Quint to set one before requesting”	No region is recorded for your partner account	Contact Quint.
”Your partner account is not active — nothing was sent”	Your partnership is suspended or not yet active	Contact Quint.
A refusal naming a slug already in use	A live workspace uses that slug	Choose another slug.
A refusal naming the licence, sector or quota	The request exceeds what your partner account allows	Contact Quint to review your licence tier or quota.

​

Next

• The Managed customers board
• Open a customer’s dashboard