{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":18359,"path":"governance-risk-compliance/smart-assessment-engine/sae-scope-items.md","title":"Scope items in an assessment","bundle":null,"doc_type":null,"release":"australia","body":"\n# Scope items in an assessment\n\nThe scope of an assessment is the specific record that the assessment targets — such as a control, vendor, or entity. Scope items keep that record in view for responders and reviewers, and other SAE features use scope to behave intelligently.\n\n## Scope item overview\n\nAn assessment is never a questionnaire in the abstract — it is always completed *about* something specific. That \"something specific\" is the assessment's scope. A scope item is a pointer to a single source record. It is identified by a table \\(for example, the *Vendor* table\\) and a record on that table \\(for example, *Acme Corp*\\). An assessment can have one scope item, multiple scope items, or none.\n\nTwo assessments built from the same template can have completely different answers because they are scoped to different records. For example, a vendor security questionnaire scoped to *Acme Corp* and the same questionnaire scoped to *Globex Inc* share the questions but capture each vendor's own answers.\n\nA useful way to think about it:\n\n-   **The template**\n\n    Defines *what* to ask \\(questions, sections, instructions\\).\n\n-   **The scope**\n\n    Defines *about what* to ask it \\(the source record\\).\n\n-   **The responder**\n\n    Provides the answers.\n\n\nScope items aren't configured on a template or template category. Scope is assigned at the time the assessment is created — typically through an assessment trigger, a Flow Designer action, or a public API call. After an assessment is created, responders, reviewers, and administrators can view its scope items but can't add, change, or remove them from the responder experience.\n\n## Where scope items appear in the assessment\n\nScope items appear in several places so that responders and reviewers can keep the source record in view as they work.\n\n-   **Assessment header**\n\n    The header at the top of the assessment shows scope items inline alongside the assessment title and status. Each scope item is shown as a label \\(the source table name\\) and a value \\(the source record name\\).\n\n-   **Navigation panel \\(combined assessments\\)**\n\n    The left navigation panel renders scope items on each assessment card so responders can distinguish constituent assessments. When assessments share the same template, scope items appear in a stacked layout. When templates differ, scope items appear in a tabbed layout.\n\n-   **Section viewer**\n\n    The section viewer header displays scope items for the constituent assessment in a tabbed layout. This keeps the source record in view while responders answer questions.\n\n-   **Details / contextual sidebar**\n\n    The Details section includes a Scope card that lists every scope item as a label-value pair. When reference fields are configured for a scope item, an additional reference information card appears. It surfaces the configured fields from the source record in a breadcrumb-style layout \\(for example, **Department** > **Cost center** > **Manager**\\).\n\n-   **Assessment task list**\n\n    The list of assessments that a reviewer or assignee sees before opening any one of them surfaces scope item fields as columns on each row. This makes it easier to triage and prioritize work across many assessments without having to open each one.\n\n\nIn the assessment header, navigation panel, and section viewer, no more than three scope items are shown at a time. If an assessment has more than three scope items, the additional items are summarized as a **+ N more** indicator. Selecting the indicator opens a tabbed popover that lists every scope item on the assessment.\n\n## Setting scope items on an assessment\n\nScope items are set when the assessment instance is created. The supported entry point is Assessment trigger or Flow Designer action. These pass scope items as an input parameter when triggering the assessment.\n\nEach scope item is an object with a **table** value \\(the source table name\\) and a **record** value \\(the sys ID of the source record\\). Scope items are cascade-deleted when the assessment instance is deleted.\n\n## Roles and access\n\nScope items follow the access model of the assessment instance:\n\n-   **sn\\_smart\\_asmt.assessment\\_admin**\n\n    Can view and modify scope items at the table level. Typically used by administrators who configure assessment triggers and Flow Designer actions.\n\n-   **sn\\_smart\\_asmt.actor**\n\n    Can view scope items on assessments assigned to them. Scope items are read-only from the responder experience.\n\n-   **sn\\_smart\\_asmt.assessment\\_reader**\n\n    Can view scope items on assessments that they have read access to. Scope items are read-only.\n\n-   **sn\\_smart\\_asmt.reassign**\n\n    Can view scope items as part of the in-progress assessments that they reassign to another user.\n\n\n## Tables used by the scope feature\n\nThe assessment scope is supported by two tables in the Smart Assessment Engine data model:\n\n-   **Scope item \\[sn\\_smart\\_asmt\\_scope\\_item\\]**\n\n    Identifies a single source record by table name and record sys ID.\n\n-   **Assessment instance to scope item \\[sn\\_smart\\_asmt\\_m2m\\_instance\\_scope\\_item\\]**\n\n    Links an assessment instance to one or more scope items.\n\n\nFor a full list of tables installed by Smart Assessment Engine, see [Tables installed in Smart Assessment Engine](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/smart-assessment-engine/tables-installed-in-smart-assessment-engine.md).\n\n"}}