Skip to content

Approvals

Approving a project

Approval For When
Resource manager every project When its box is ticked in Settings → Customer → Approvals; cleared, an order is approved as it was ordered (when that cannot be done, the step comes back to a super admin with the reason on the project). Confirms the project's name and type, chooses the site and cluster and the internet address pool (set to auto when the ordered base subnet is not one the platform provides), confirms or changes the resources and the project admin, and names the organization's sales rep when a cloud organization has none.
Sales rep cloud projects When its box is ticked in Settings → Customer → Approvals.
Support engineer corporate projects When its box is ticked in Settings → Customer → Approvals.

A ticked step waits for the project's (or its organization's) own person in that role, else anyone with the role who can sign in, else a super admin; nobody in a cleared role is asked. Provisioning starts by itself after the last approval. A person in several roles approves once for all the steps waiting for them. A super admin may approve any step; they are asked only in the roles ticked for them.

The addresses of the order are reserved when the resource manager approves. A request can be rejected with a reason by those who approve it; the organization's admins are told. While it waits, the organization's admins (or a resource manager) can cancel it. Rejected and cancelled requests can be archived.

Administration → Approval requests lists everything waiting (new organizations, new projects, resource changes, network changes, projects to provision, L2 channels waiting for a VLAN, deletions, moves of a project to another organization) with who approves now, and Waiting for me; the menu shows how many wait for you. Approved requests and rejected or cancelled ones of the last 30 days have their own tabs.

When the last approval is given, provisioning starts by itself; Provision again appears on the project only when it could not start or failed (see Ordering and provisioning).

flowchart TB
    O[Order<br/>org admin or resource manager] --> RM{Resource manager<br/>names, places, confirms}
    O -. resource manager's box cleared .-> AO[Approved as ordered<br/>else the step goes to a super admin]
    AO --> S
    RM -- reject --> X[Rejected<br/>org admins told]
    RM -- approve --> S{Box ticked for the project's type?<br/>cloud: sales rep · corporate: support engineer}
    S -- yes --> SR{Sales rep or<br/>support engineer}
    SR -- reject --> X
    SR -- approve --> A[Last approval]
    S -- no --> A
    A --> P[Provisioning starts by itself]
    P -- failed / could not start --> R[Provision again on the project]

The kinds of approval requests

flowchart LR
  AR[Administration →<br/>Approval requests]
  AR --> N1[New organizations<br/>resource manager, sales rep]
  AR --> N2[New projects<br/>resource manager, sales rep,<br/>support engineer]
  AR --> N3[Resource changes<br/>resource manager]
  AR --> N4[Network changes per site<br/>speed, main subnet, subnets,<br/>corporate networks, L2]
  AR --> N5[L2 channels waiting for a VLAN<br/>support engineer]
  AR --> N6[Deletions<br/>resource manager]
  AR --> N7[Project moves<br/>resource manager,<br/>sales rep of the new organization]
  AR --> N8[Projects to provision<br/>could not start or failed]

Who can do what

What each role does with each kind of request. asks: starts the request; approves: is asked to approve; may: may approve without being asked; does: carries it out; told: gets an e-mail.

Platform users

Request Super admin Resource manager Support engineer Sales rep Key account manager
New organization may approves, assigns its platform users — approves (cloud, when sales approval is on) —
New project asks, may (gets the resource manager's step when an order cannot be approved as ordered) asks, approves (when ticked) approves (corporate, when ticked) asks (their organizations), approves (cloud, when ticked) —
Provisioning (starts by itself) told told told told told (cloud projects)
Provision again does — does — —
Resource change asks, may approves — asks (their organizations) asks (their organizations)
Network change may approves sets the VLAN of L2 channels asks (their organizations) asks (their organizations)
Internet gateway size does — — — —
Project move asks, may asks, approves — approves (the new organization's, when it has one) —
Deletion asks, may asks, approves — asks (their organizations) —
Status (lifecycle) does does — — —
Stage does does does does (their organizations) —
Review date does does — does (a POC of their organizations, up to 3 months after it was made) —
Super admin role given or taken away asks, confirms (see Roles) — — — —

Organization users

Request Organization admin Project admin Read only
New organization asks (registering) — —
Joining an organization approves — —
New project asks — —
Provisioning (starts by itself) told (the access details, when not the project admin) told (the access details) —
Provision again does does —
Resource change asks asks (their projects) —
Network change asks asks (their projects) —
Deletion asks — —
Status (lifecycle) told (expiration notices) — —

On provisioning, every platform user of the project is told (see Ordering and provisioning).

Registration requests

A registration request that is not approved is deleted; only the portal's log keeps it (e-mail, organization, tax ID, the checks' result):

  • a request refused by the staff — at once;
  • a request whose e-mail is not confirmed within 48 hours — by the daily run;
  • a join request declined by the organization's admin — at once, with its applicant.

A request waiting for the staff's decision stays until it is decided. A registration is decided once: if one person approves it while another refuses it, the decision made first stands, and only its notice is sent.

The portal checks every registration — what is entered and how the form is sent. An automated submission gets the usual answer and nothing is made (the log keeps the attempt). Other signs of a fake or hostile request add to a score; a suspicious request is marked, and the staff see the score and the reasons on the organization waiting for approval and in the approval e-mail.

There is no separate report on registrations. The super admin's weekly report (Settings → Reports) counts the organizations in its Totals, with the new ones of the period.

flowchart TD
    R[Registration form sent] --> C{Checked}
    C -- automated --> X[Usual answer, nothing made<br/>log only]
    C -- otherwise --> E[E-mail to confirm]
    E -- not confirmed in 48 h --> D1[Deleted, log keeps it]
    E -- confirmed, new tax ID --> W[Organization waiting for approval<br/>score and reasons shown to the staff]
    E -- confirmed, known tax ID --> J[Join request to the organization's admins]
    W -- approved --> A[Organization admin can sign in and order]
    W -- refused --> D2[Deleted, log keeps it]
    J -- accepted --> U[User of the organization]
    J -- declined --> D3[Deleted, log keeps it]

Changing and deleting a project

  • Resources: the project's admins ask for a change of a resource pool, or order another pool (another cluster or a new site); a resource manager approves it (and may change the figures) or rejects it. A resource manager can also change the resources directly; every change is a new version of the project's resource records.
  • Networks: project admins ask to add or delete a public subnet (choosing its base subnet, or auto), replace the main one, change the speed, add or delete a corporate network, add or remove an external L2 channel; a resource manager (or a super admin) approves. An Internet or corporate-network request is approved with Approve…, which asks for the delegated range when there is one to choose. An external L2 channel then waits for its VLAN, set by the support engineer; it is made as soon as its VLAN and subnet are set. The internet gateway type, an L2 channel's subnet and a new internal L2 channel (between two of the project's networks on two sites) need no approval. An approved change normally starts at once. If the platform does not allow changes at that moment (for example, it is read only), the change is shown as waiting, with the reason, and starts by itself within a few minutes once the platform allows it; a resource manager can also press Run. Either way it is made once. This holds for every kind of network change, including removing an L2 channel and changing its endpoint: an approved change that cannot start yet waits, with the reason, and starts by itself or with Run. A network request is decided once. If it is cancelled or rejected while someone approves it, the cancellation or rejection stands: nothing is allocated or changed, and the page says the request was already decided. A change is made once: pressing Retry again while it runs does not start it twice. If replacing the main network stops after the new prefix became the main one (for example while the network and the gateway are made again), Retry goes on from there: it makes the network and the gateway on the new prefix without removing anything again. The steps of the earlier attempt stay on the request. The switch to the new main prefix happens in one step: if the portal stops during it, the old prefix stays the main one and Retry makes the whole replacement again. A project has one internet connection per site: the speed, the main subnet and the additional subnets are asked for on the row of the project's own site (the site it was ordered on), and every request belongs to that site; on the project's other sites, changes are asked through support.
  • Bandwidth: the edge gateway limits the project's internet with a shaper (fq-codel) on the egress of both its sides — towards the exchange (the project's upload) and towards the project's main network (its download) — at the project's bandwidth. When a bandwidth change is approved, the record changes, the edge gateway gets the new value at once and the project group's quota record follows.
  • Deletion: Request deletion on the project (its organization admins, the organization's sales rep, a resource manager or a super admin; not a key account manager or a project admin), confirmed by typing the project's name. It is always a request first, with the plan of everything that will be deleted (VMs, backups, images, networks, rules, users, the group); it starts only after a resource manager approves it (a resource manager or super admin who asked may approve their own request). While it runs the project's status is Being deleted. Exactly the listed resources are deleted, the platform is checked again for anything left, then the portal releases the addresses and closes the records, and the project is Archived. Projects are never removed from the portal: they stay as records, shown in the lists on demand. When the platform cannot be read during the deletion, the deletion stops at that step (it can be run again); it never goes on to the permissions, users and group without knowing what is left. A deletion request is decided once. If it is cancelled or rejected while someone approves it, the cancellation or rejection stands: the approval changes nothing, nothing is deleted, and the page says the request was already decided. Two approvals at the same moment start one deletion. Deleting a project removes its L2 channels first, on both ends - including the gateway and VLAN network on the site's management platform. If a channel cannot be removed (for example, that platform is read only or does not answer), the deletion stops and can be retried; nothing is marked removed that is still there. Then the project's VMs are terminated, and with them the provider's gateways connected to the project's networks (the egw, the cgw and the L2 gateways), whatever their names: they are deleted before any of the project's networks is deleted, as they hold addresses on the project's networks. If a deletion fails half way (the platform did not answer, for example), the project stays Being deleted. A resource manager or a super admin then has Retry deletion on the top row of the Delete card: after typing the project's name, what is left of it on the platform is listed again and deleted; what is already gone is skipped.
flowchart TB
  A[The project's admins ask] --> K{Kind}
  K -- resources --> RM1{Resource manager}
  K -- networks, on a site's row --> RM2{Resource manager<br/>or super admin}
  K -- "deletion (org admin, sales rep,<br/>resource manager)" --> PL[Plan of everything<br/>to delete] --> RM3{Resource manager<br/>or the RM / super admin who asked}
  RM1 -- approve --> C1[Carried out at once]
  RM2 -- approve --> L2{L2 channel?}
  L2 -- no --> C1
  L2 -- yes --> V[Support engineer<br/>sets the VLAN] --> C1
  RM3 -- approve --> DEL[Being deleted: listed resources deleted,<br/>platform checked again,<br/>addresses released, records closed] --> ARC[Archived]

Moving a project to another organization

A resource manager (or a super admin) asks to move a project from its Edit project page: the move button next to Save opens the list of organizations (tax ID first, sorted by name). The move waits for the resource manager and the new organization's sales rep (when it has one); the person asking approves in the roles they hold, and one person in both roles approves once. The request is shown on the project and among the approval requests; it can be rejected with a reason. One refusal ends a move request, even when an approval arrives at the same moment: the approval made meanwhile neither undoes the refusal nor moves the project. When it is approved the project moves; its project admin stays when they can be one in the new organization, otherwise the new organization's admin (or another of its users) takes over. When a project moves to another organization, the people of the former organization leave it: their access to the project ends and they no longer receive its access details. The new organization's project admin receives them. Platform users of a corporate project keep their access where they had it.

sequenceDiagram
    actor RM as Resource manager
    participant Portal
    actor SR as Sales rep of the new organization
    RM->>Portal: Edit project, move to another organization (list: tax ID · name)
    Note over Portal: the resource manager's approval is given by asking
    alt the new organization has a sales rep
        Portal->>SR: e-mail: the move waits for your approval
        SR->>Portal: approves (or rejects with a reason)
    end
    Portal->>Portal: the project moves, its project admin checked

Settings → Customer

  • Approvals (the Approvals block of the Customer tab): a box per approval step — the resource manager (every project), the sales rep (cloud projects), the support engineer (corporate projects). Ticked: every new order waits for that role (the project's or organization's own person, else anyone with the role who can sign in, else a super admin). Cleared: nobody in that role is asked; without the resource manager's step an order is approved as it was ordered, and when that cannot be done the step comes back to a super admin with the reason on the project. The Approvers column lists the active users of each role; a box can be ticked only while at least one active user holds the role.
  • New users (its Customers block): whether users can be added (a record without sign-in, invited later) or only invited.
  • igw ssh ports are on the Security tab: the range a new internet gateway's ssh port is chosen from.
  • E-mail to organization users and e-mail to platform users are switches on the Mail tab (see Project lifecycle): mail a switch does not allow is kept on the portal and logged, never sent; the expiration notices follow the first switch.
  • Corporate e-mail domains are in the Customers block: an organization registered from one of them is corporate.

The tabs of Settings are Customer, Security, Mail, Reports, Backups and Portal; they are described in the portal reference.