Columns
Ticketing
Central opens one ticket per incident in your ticketing system, keeps its status in step both ways and copies notes and comments. Each client can go to its own system.Routes which clients' incidents open tickets where
| Connector | Clients | Opens tickets for | From severity | State |
|---|
Tickets
| Ticket | About | Client | Severity | In the console | In the ticketing system | Opened |
|---|
Delivery log
| When | Connector | Client | Ticket | What | Detail |
|---|
Clients
| Client | Service | Console | Subscription | Features | Endpoints | Expires | Resources |
|---|
Policy templates
Capture a policy from one client, then push it to many: as its own policy (each client's groups decide which endpoints get it) or as their Default policy.Partners
Distributors, resellers and MSSPs. A partner's staff see only that partner's clients (and those of partners under it).| Partner | Kind | Country | Under | Clients | Managed | MDR | Staff | Status |
|---|
Portal users
| User | Organisation | Role | Signs in to | Last sign-in | Status |
|---|
Licenses
| Client | Deployment | License | Endpoints | This month | Reported |
|---|
Monthly usage and billing
Download CSV| Client | Partner | License | Billing | Licensed | Peak | Daily average | Billable | Reported by |
|---|
Licensing and payments
Orders
Open the store| Order | Client | Plan | Amount | Status | Console |
|---|
Sales leads
| When | Company | Contact | Interest | Assigned to | Status | Notes |
|---|
Regions
Each region is a platform server (a cell) on any cloud: AWS, Oracle, Azure, Google or your own. New clients go to the active region that serves their country and has room.| Region | Cloud | Countries | Clients | Health | Status |
|---|
To add a region: install the platform on a Linux server there (deploy/cell in the repository: one command on any VM), give it Platform__CellKey (at least 24 random characters) and Platform__ControlUrl (this portal's address), then add it here with the same key.
Dedicated servers
Clients on their own cloud server, on AWS or Oracle Cloud in the location chosen for them: built by the platform when the order is paid, linked to Central, renewed through their license check-in.| Client | Server | Address | Status | Central | License |
|---|
On-premises clients
| Client | Console | Install link | Used |
|---|
Home
Documentation and resources
Support
| Request | Subject | Client | Priority | Status | Answered by | Updated |
|---|
Team
The people of your organisation who sign in to this portal. An administrator manages accounts and opens the console as an administrator; a member reads documentation, asks for support and opens the console as an analyst.| Account | Role | Two-step sign-in | Last sign-in | Status |
|---|
Your account
Profile
Two-step sign-in
Portal content
Documents Only signed-in clients and partners can read them. Sales material and price lists go to partners only. A draft is not shown.
| Title | Category | For | Version | File | Status | Opened |
|---|
Announcements Shown on the home page of the portal: news, maintenance windows, incidents and releases.
| Title | Kind | For | When | Status |
|---|
Platform activity
| When | Who | Action | Client | Detail | Address |
|---|