Support Access Levels

Master Admin is Nasiya’s internal tool that lets authorised Nasiya staff (“Nasiya admin”) open your organisation’s workspace — the same screens your own team sees — to provide support, diagnose an issue, assist with implementation, or maintain the security of the Service. This is sometimes called “View As.”

Nasiya admin cannot open Master Admin on your organisation at all unless you have an open access window — Master Admin is otherwise inactive for your organisation, including for read-only inspection. An admin on your team opens a window from the Request Admin Support button available on every page of your workspace, or from Settings → Organisation, choosing the level — Read-Only (default) or Full — for that window. Any member of your organisation can also submit a request from that same button; it notifies your admins and Nasiya, but only an admin’s own submission actually opens a window.

A window stays open for 24 hours from when it was opened, or until an admin on your team revokes it early from Settings → Organisation — whichever comes first. There is no standing, always-on access: every session traces back to a specific window your organisation opened.

Under Read-Only Support Access, Nasiya admin may open your workspace to inspect:

• Your workspace configuration and settings
• Roles and job postings
• Candidates, applications, and pipeline stages
• AI-generated outputs (scores, flags, interview questions, assessment results)
• Connected integrations (ATS connections, Chrome extension activity)
• Logs, including your organisation’s own audit log
• Feedback and Field Notes submitted within your workspace

Nasiya admin does not create, edit, delete, or otherwise change anything in your workspace under this level — not a candidate record, not a role, not a setting — without your explicit instruction or approval on that specific action. This is enforced at the request level in Nasiya’s backend: while your organisation is set to Read-Only, every request that would change data is rejected outright when made through Master Admin, regardless of which Nasiya admin is making it.

Full Support Access includes everything permitted under Read-Only, plus your explicit authorisation for Nasiya admin to make changes reasonably necessary to configure, test, troubleshoot, or implement a fix or feature you have requested in your workspace. Examples include correcting a misconfigured setting, applying a data fix you’ve asked for, or setting up an integration on your behalf.

Full Support Access is not a general licence to modify your data at will — it exists so Nasiya can act on requests you’ve actually made, without a back-and-forth over screen-share for every small change. It is also still bound by the same 24-hour window as Read-Only — Full Access does not mean standing access. You can revoke it, or switch a future window back to Read-Only, at any time.

Every time you set or change your Support Access level — including your initial choice during onboarding — Nasiya records who made the change, when, and what the level was set to, in your organisation’s own audit log at Settings → Audit Log. This record is independent of anything a Nasiya admin does afterward, so you always have a clear account of what access was authorised and when.

This page is Nasiya’s plain-language operational explanation of Support Access and is kept in sync with how the underlying system actually behaves. If anything here appears to conflict with your signed services agreement, the terms of that agreement govern. Questions can be sent to support@nasiya.co.