Respondent mode and portals

Two surfaces exist to keep people out of parts of CyberGuard they do not need. Respondent mode hands a contributor only the requirements they were assigned, inside a single shared audit. Custom portals replace the full sidebar with a curated grid of tiles for a given audience.

Respondent mode

The point is to run one audit that many people contribute to, rather than a copy per team. An analyst or higher starts the audit, then dispatches groups of requirements to the users or teams who can actually answer them. A contributor needs only the respondent role on the domain.

For the respondent

Assigned work lands under Overview → Respondent View. Each card shows the audit’s framework, the domain it belongs to, who the assignment names, and a progress bar counting assessed requirements against the total. The button adapts to where the assignment stands — Start Assessment on an untouched one, Continue Assessment once work is under way, and Review responses when the round is finished. If nothing appears, either nothing has been dispatched yet or a permission is missing.

Inside an assignment, respondents answer the compliance result on their own requirements and attach evidence or applied controls. They can reuse existing controls and evidence from the domain as well as create new ones, which is deliberate — it keeps the same control from being described five times by five teams.

A user who spends all their time here can make it the landing page: My profile → Settings → Preferences → Default landing → Respondent mode.

Assignment states

State	Meaning
Draft	Being prepared. Actors and requirements can still be edited, and the assignment deleted.
In Progress	Launched; the respondent is working on it.
Submitted	Handed back for review.
Changes Requested	The reviewer asked for corrections and expects a resubmission.
Closed	Reviewed and accepted.

Once an assignment leaves Draft, its scope locks: the agreed set of actors and requirements stays fixed while work is in flight. To change it, a reviewer reopens the assignment to Draft, which unlocks editing and reassignment.

Custom portals

A portal is a grid of tiles you compose yourself — a home screen that says “here are the three things you do here”. Portals come in two flavours built in the same editor: internal portals sit behind login, and public portals are read-only pages anyone with the link can open. The public flavour is covered on its own page, Trust center.

Building one

Authoring lives at Extra → Manage portals. Under Internal portals, use Add to create one, name it, and build it out of groups, each holding tiles — Add group and Add item. Every tile takes an Icon, a Title, a Kind and a target that depends on the kind:

Create opens the creation form for a model, for example a new incident.
Navigate links to a model’s list page or a built-in page.
Questionnaire launches an audit from a framework you choose.
External opens an external link in a new tab.

The header carries an Edit / Preview / Settings switch, a Save button, and Publish or Unpublish to control availability. Point a person or the whole organisation at a portal by setting Default landing to Portals, in profile preferences or in general settings.

Audits — the assessment respondents contribute to.
Trust center — the public flavour of a portal.
User groups — granting the respondent role on a domain.
Feature flags — turning either surface on.