The demonstration runs on its own fictional data set, which lives inside the application: it reads and writes there, never in a real client’s data. Below you choose the scenario and the profile of the visit.
Open the task register in the demonstrationA scenario is one link of the fictional set: the client, the contracted bundle and the frameworks it opens. The profile is chosen inside it — changing profile does not touch the set.
This is the starting scenario. The others join as new links of the fictional set.
Read from the application’s own permission matrix, imported unchanged — the same one the menu and the routes read. This is a presentation, not validation of the real authorisations.
41 areas to read · 27 to write · 24 to delete
Where this profile writes:
Compliance Journey · Assessments · Recommendations · Action Plan · Tasks · Evidence · Documents · Reports · Audit Package · Risk Management · Incidents · Vulnerabilities · Assets & access · Business continuity · Security in acquisition · Suppliers · Supply Chain · RoPA Registry · Data Subject Requests · Training · Framework guidance · Question DB · Onboarding · Roles & Access · Settings · Legal repository · Policy attestations
gama.admin.demo@gama.invalid
Fictional set kept in memory inside the application. No request leaves here for real client data, files or credentials.
12 fictional records · 7 areas
The deadlines below are read with the same calculation the application uses in its own registers, imported unchanged: between the two modes the data origin changes, the rules do not.
Changing a field of the fictional organisation writes to the local set; restoring brings back the initial data.