Skip to main content

Administration

Who can see which findings, and who can accept risk on them? Answer that badly and you get one of two failures: everyone is an administrator, or the people who fix things cannot see what is broken.

Access in Dwaar has one rule that explains everything else: a group gives its members one role on the organizations you pick, and on all their children. Access is additive. There are no deny rules, so you never have to work out which rule won.

The model​

TermWhat it is
TenantYour whole Dwaar account. Whoever creates it at their first sign-in becomes its first administrator. If your company used Dwaar before it used the console, its first administrator is the person Dwaar named as your organization's administrator, and nobody else can open the console until they have signed in.
OrganizationA node in the tree inside your tenant, such as a business unit or a team. The tree starts at the root organization, which is created with the tenant and always exists.
PermissionOne allowed action, such as findings:read.
RoleA named set of permissions. It grants nothing until a group uses it.
GroupOne role, on chosen organizations, for chosen members.
MemberA person who has signed in to your tenant. An invited person becomes a member at their first sign-in.
Service accountA machine identity that joins groups like a person does and signs in only with its own API keys.

Notice what is missing: nobody has a role directly. Even an invite, which asks you for a role, grants it through a group on each organization you pick. A member with no group has no access yet, and the console says so. Someone who signs in after their invite expired lands like that: add them to a group.

Where to go​

Try this next​

Open Settings › Members, look at the Groups section, and read it as sentences: "this group gives this role on these organizations". If one reads wrong, you have found your first access fix. Then start with Organizations.