Skip to content
English
  • There are no suggestions because the search field is empty.

Before you start - access, roles, and what to have ready

Summary

Almost every setup task depends on something being in place first: an account, a role with the right permissions, or a plan that includes the feature. This article covers what to sort out before your first working session, so you are not stopped halfway through a task waiting on someone else.

Before you start

You need a CyberHQ.ai account. If you don't have one, someone in your organization with the Manage Users permission invites you by email address and assigns you a role at the same time.

1. Get an account

Accounts are created one of two ways, depending on how your organization is configured:

  • Invite-only: an administrator invites you directly. You receive an email invitation.
  • Self-service: you can sign yourself up, provided your email domain is on your organization's allowed list.

If you are unsure which applies, ask whoever administers the platform for your organization. If single sign-on enforcement is turned on, you sign in through your organization's identity provider rather than with a password.

2. Confirm your role covers what you need

Permissions come from the role assigned to your account, and roles are configurable: so "administrator" in your organization may not mean exactly what it does in another. Two thresholds matter most:

  • Reaching Configure at all requires the Manage Users or Manage Tenant permission. Without it, you can work in the platform but cannot configure it.
  • Some individual sections require further permission on top of that, so two administrators commonly see a different set of options.

If you find a section you expect and cannot reach, check with your administrator first: the role assigned to you is the most common reason two people see a different set of options.

3. Check what your plan includes

Features not included in your plan don't disappear: they stay visible in the menu with a lock, and opening one explains why it's locked, so you can see what exists. Three capabilities can also be added to the Professional plan on their own: Full compliance, Vendor risk + threat intel, and Attack simulation. Full compliance and Attack simulation also have to be turned on for your organization; buying the add-on alone doesn't turn them on, so ask your account team. The endpoint sensor and the browser extension are not add-ons: both are included on every plan.

Worth knowing before you plan your first week: monitoring reaches your people through a browser extension, an endpoint sensor, or both. The browser extension covers activity in the browser. The endpoint sensor extends that to desktop AI applications, command-line tools, other browsers, and locally running models: and clipboard activity, running processes, installed software, and privilege events come only from the endpoint sensor.

4. Have these ready

  • Who administers the platform for your organization: the person who can grant access, adjust roles, and confirm plan questions.
  • How devices are managed: whether you deploy software centrally (through a device-management tool) or people install it themselves. This determines which deployment path you follow.
  • Who should be notified when something happens in the platform, and where to connect your notifications: a Slack or Teams channel you connect into CyberHQ.ai, an email address, or a ticketing queue. This is about your own team's alerting, not how you reach us, for that, see Get to know Support.

Confirm you're ready

You can sign in, reach the areas your work requires, and you know who to ask when you can't.

Related

  • Welcome to CyberHQ.ai
  • An endpoint sensor isn't reporting