# ServiceNow Administration Scoped. Governed. In-platform. YouDesign Blueprints runs inside the customer's ServiceNow environment. This page covers what admins, platform owners, and security reviewers need to know about its runtime model, data stores, and access controls. {% hint style="info" %} This page is technical reference for administrators, platform owners, security reviewers, and governance leads. End-user role behavior lives on [Roles and Permissions](/blueprints/start-here/roles-and-permissions.md). Data residency and security review topics live on [Security and Data Handling](/blueprints/admin-and-governance/security-and-data-handling.md). {% endhint %} ## What YouDesign Blueprints is YouDesign Blueprints is a scoped ServiceNow application with the application scope `x_inpi_ydbp`. It runs inside the customer's ServiceNow environment and uses ServiceNow-hosted UI and backend components for blueprint design, review, and the Commit workflow. ## Architecture at a glance | Area | What it means in practice | | ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Application model** | Scoped ServiceNow application under `x_inpi_ydbp` | | **Frontend runtime** | UI loaded inside the ServiceNow shell under the scoped route /x\_inpi\_ydbp\_app.do | | **Backend runtime** | Scoped Scripted REST APIs and platform server-side scripts running on the ServiceNow instance | | **Primary data stores** | Scoped application tables such as `x_inpi_ydbp_templates`, `x_inpi_ydbp_blueprints`, `x_inpi_ydbp_blueprints_content`, and per-user settings in `x_inpi_ydbp_user_settings` | | **Authentication model** | ServiceNow session-based access. The application uses the active user's session and platform token. | | **Authorization model** | Role-based access. ACLs and platform controls also apply. | ## What admins should know about the runtime model The application runs entirely inside ServiceNow: * Users open the application through ServiceNow. * The UI is served inside the ServiceNow shell. * App APIs are called through scoped endpoints under `/api/x_inpi_ydbp/youdesign_blueprints/...` * Blueprint and template records are stored in scoped ServiceNow tables. In other words, the application runs entirely on the ServiceNow platform, no external services or separate hosting required. ## Main administration concerns ### Access and role assignment The main runtime roles are: | Role | Purpose | | --------------------------------------- | -------------------------------------------- | | `x_inpi_ydbp.blueprint_template_editor` | Configure templates and governance | | `x_inpi_ydbp.blueprint_editor` | Create and edit blueprint content | | `x_inpi_ydbp.blueprint_commit` | Review and commit approved blueprint changes | | `x_inpi_ydbp.blueprint_viewer` | Read-only access | As with any ServiceNow application, role assignment should follow least-privilege principles. ### Data ownership and storage The application stores: * Template definitions * Blueprint metadata * Blueprint canvas content and layout * Staged future-state and relationship work * Per-user application preferences such as theme, language, accessibility settings, favorites, and sort preferences ### Platform governance YouDesign Blueprints is not an external design tool that connects to ServiceNow. It is a scoped ServiceNow application with its own tables, endpoints, roles, and Commit workflow. ## Architecture and enterprise review The application is designed with several boundary controls in place: * Scoped app isolation through `x_inpi_ydbp`. * Role-based access to creation, editing, viewing, and Commit workflows. * In-platform persistence for templates, blueprints, and user settings. * Separation between normal draft saving and explicit Commit actions. * Backend-centric integration with ServiceNow data and metadata. The browser does not call external services directly. These properties make the application easier to review for boundary control, access governance, and predictable behavior. ## Typical admin checklist Before go-live or review sign-off, confirm: * The required Blueprints roles are assigned to the correct user groups. * The scoped application is installed and accessible through the intended ServiceNow entry points. * The required tables, Scripted REST resources, and supporting backend scripts are available in the target instance. * The intended users can save drafts, review compliance, and commit changes according to their assigned role. Make sure security and privacy reviewers have also read [Security and Data Handling](/blueprints/admin-and-governance/security-and-data-handling.md). ## What this page does not replace This page is an overview. It does not replace: * your ServiceNow role-governance process * your instance-specific ACL review * your change-management process * your internal security approval workflow --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.ins-pi.com/blueprints/admin-and-governance/servicenow-admin-guide.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.