--- sourceDocument: Australia Build or modify applications sourceDocumentLink: https://www.servicenow.com/docs/r/australia/application-development Release : - australia ft:locale : - en-US ft:publication_title : - Australia Build or modify applications ft:clusterId : - cadev bundleId : - cadev workflow : - Development, Data, and Analytics --- # Installed properties and tables # Properties, tables, and roles installed with Build Agent {#ariaid-title1} Release version: Australia Updated November 2, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Properties, tables, and roles installed with Build Agent The Build Agent installation in ServiceNow Australia release provides a set of system properties, tables, and roles designed to control operational settings, manage data, and define access permissions. This enables customers to configure execution parameters, monitor agent activities, and secure access to Build Agent features. Understanding these components helps customers optimize Build Agent performance and maintain proper governance. Show full answer Show less ## System Properties System properties for Build Agent are accessed via the **sysproperties** table and are scoped to Build Agent (Trial). Properties control key operational limits such as tool execution timeouts, prompt limits per user, keyword search defaults, instruction and skill limits, script execution toggles, and implementation job monitoring. Most properties are readable and writable by users with the **snglider.admin** role, except for prompt limits and tier override properties which are read-only for admins. * **Tool execution:** Configures max execution times for various Build Agent tools. * **Prompt limits:** Defines rolling window periods and max prompts per user in production and non-production instances. * **Keyword search:** Sets default limits on search results and content field lengths. * **Instructions and skills:** Controls enabling of dispatched instructions and limits on active rules and skills. * **Script execution:** Enables or disables the runscript tool per instance. * **Implementation job monitor:** Manages scheduled job activity and thresholds for work item monitoring. ## Main Tables The Build Agent uses multiple tables within the **snbuildagent** scope to store data related to conversations, work items, plans, instructions, skills, telemetry, and more. These tables support the management and tracking of agent activities and user-defined inputs. Key tables include: * **Build Agent Activity:** Records units of work and their outcomes. * **Build Agent Plan:** Stores agent-generated plans with state and order. * **Build Agent Work Item Dependency:** Manages dependencies and ordering of work items. * **Build Agent Instruction and Skill:** Contains admin-defined instructions and skills available to the agent. * **Telemetry Tables:** Capture usage metrics for events and tasks. * Additional tables manage script requests, conversation change logs, IDE file mappings, and user-specific instructions. ## Access Control and Roles Build Agent (Trial) requires the **snglider.admin** role for all features, with no separate customer role. Access is controlled by role and ownership: * **Role only:** Users with **snglider.admin** can access plans, work items, instructions, and telemetry data. * **Role and ownership:** Conversations, messages, and checkpoints require users to own the records to view or modify them. * **Hidden:** Internal records and background runs are not visible to customers. Notably, users with the same admin role cannot view each other's conversations or messages, ensuring data isolation. Even admins must own conversations to make changes. Most system properties allow read/write by admins, except some prompt limits and tier override settings which are read-only. System properties installed with Build Agent control operational settings and resource limits. Tables store conversation, message, checkpoint, and telemetry data. Roles define access control for properties and features. ## System properties {#ba-properties-installed-with__ba-system-properties} To access these properties, enter sys_properties.list in the navigation filter to open the System Properties \[sys_properties\] table. All properties are in the Build Agent (Trial) scope. {#ba-properties-installed-with__table_ba-prop-tool-execution__entry__6} | Property | Type | Default | Read role | Write role | Description | |-|-|-|-|-|-| | sn_build_agent.tool.execution.timeouts | String (JSON) | `{"run_query": 120000, "get_knowledge_source": 120000, "create_new_servicenow_app": 300000, "default": 240000}` | sn_glider.admin | sn_glider.admin | Sets the maximum execution time (in milliseconds) for each tool. | [Table 1. Tool execution] {#ba-properties-installed-with__table_ba-prop-tool-execution} These properties can be read by admin but not written. {#ba-properties-installed-with__table_ba-prop-prompt-limits__entry__6} | Property | Type | Default | Read role | Write role | Description | |-|-|-|-|-|-| | sn_build_agent.prompt_limit_period_days | Integer | 30 | admin | None | Rolling window period (in days) used in prompt-limit calculations. | | sn_build_agent.user_prompt_limit | Integer | 100 | admin | None | Maximum prompts per user per rolling window in production environments. | | sn_build_agent.user_prompt_limit_pdi | Integer | 25 | admin | None | Maximum prompts per user per rolling window in non-production instances. | | sn_build_agent.tier_override | String | None | admin | None | Overrides the Build Agent tier. Valid options: `free` or `paid`. Setting `paid` requires the `sn_build_agent_pro` scope to be installed. No entitlement check is performed through `sn_now_creator`. | [Table 2. Prompt limits and tier] {#ba-properties-installed-with__table_ba-prop-prompt-limits} {#ba-properties-installed-with__table_ba-prop-keyword-search__entry__6} | Property | Type | Default | Read role | Write role | Description | |-|-|-|-|-|-| | sn_build_agent.keyword_search.default_limit | Integer | 10 | sn_glider.admin | sn_glider.admin | Default number of results returned by keyword search when the client omits the limit parameter. | | sn_build_agent.keyword_search.max_field_length | Integer | 2000 | sn_glider.admin | sn_glider.admin | Default maximum characters per content field when contentMode is `truncate`. Clients can override this with the maxFieldLength request parameter. | [Table 3. Keyword search] {#ba-properties-installed-with__table_ba-prop-keyword-search} {#ba-properties-installed-with__table_ba-prop-instructions-skills__entry__6} | Property | Type | Default | Read role | Write role | Description | |-|-|-|-|-|-| | sn_build_agent.instruction.dispatch_enabled | Boolean | true | sn_glider.admin | sn_glider.admin | When false, dispatched (non-interactive) work item runs skip loading instance and user skills and rules. | | sn_build_agent.instruction.rule.active_limit | Integer | 5 | sn_glider.admin | sn_glider.admin | Maximum number of active rule instructions per applies-to bucket. | | sn_build_agent.instruction.skill.active_limit | Integer | 50 | sn_glider.admin | sn_glider.admin | Maximum number of active skill instructions per applies-to bucket. | [Table 4. Instructions and skills] {#ba-properties-installed-with__table_ba-prop-instructions-skills} {#ba-properties-installed-with__table_ba-prop-script-execution__entry__6} | Property | Type | Default | Read role | Write role | Description | |-|-|-|-|-|-| | sn_build_agent.script_execution_enabled | Boolean | true | sn_glider.admin | sn_glider.admin | Per-instance switch for the `run_script` tool. Set to false to withdraw the script_execution capability on this instance, which stops the tool being offered to the agent. Withdraw-only: a production instance does not expose the capability, regardless of this setting. | [Table 5. Script execution] {#ba-properties-installed-with__table_ba-prop-script-execution} {#ba-properties-installed-with__table_ba-prop-job-monitor__entry__6} | Property | Type | Default | Read role | Write role | Description | |-|-|-|-|-|-| | sn_build_agent.implementation_job_monitor.enabled | Boolean | true | sn_glider.admin | sn_glider.admin | Main kill switch for the Implementation Jobs Monitor scheduled job. Set to false to stop all monitor activity without disabling the scheduled trigger. | | sn_build_agent.implementation_job_monitor.max_per_run | Integer | 50 | sn_glider.admin | sn_glider.admin | Maximum number of in-progress work items the watchdog scans and interrupts in a single run. Caps script execution time. Remaining candidates are caught on the next run. | | sn_build_agent.implementation_job_monitor.stall_threshold_sec | Integer | 900 | sn_glider.admin | sn_glider.admin | Seconds a work item's newest run conversation can go without a new message before the watchdog interrupts it (moves it to `needs_attention`). A conversation that never received a message is measured from when its run was dispatched. | [Table 6. Implementation job monitor] {#ba-properties-installed-with__table_ba-prop-job-monitor} ## Main tables {#ba-properties-installed-with__ba-main-tables} The following table lists tables in the `sn_build_agent` scope. The access shown is for sn_glider.admin. Descriptions are inferred from table and field names. Conversation, message, and checkpoint tables are controlled by scripts and are not listed here. {#ba-properties-installed-with__table_ba-main-tables__entry__3} | Table | What it stores | Access for sn_glider.admin | |-|-|-| | Build Agent Activity \[sn_build_agent_activity\] | Units of work the agent performs in a conversation, with outcome and retry state | Read, update, create, delete | | Build Agent Plan \[sn_build_agent_plan\] | Plans the agent drafts for a request, with state and order | Read, update, create, delete | | Build Agent Work Item Dependency \[sn_build_agent_work_item_dependency\] | Links between work items that set the order of work | Read, update, create, delete | | Build Agent ATF Test \[sn_build_agent_atf_test\] | Automated Test Framework results for an activity | Read, update, create, delete | | Build Agent Conversation Change Log \[sn_build_agent_conversation_change_log\] | Files and records the agent changed in a conversation | Read, update, create, delete | | Build Agent IDE File Mount \[sn_build_agent_ide_file_mount\] | Mapping of conversations to IDE file locations | Read, create, delete | | Build Agent Script Request \[sn_build_agent_script_request\] | Requests for the agent to run a script, with execution history | Read, update, create, delete | | Build Agent Instruction \[sn_build_agent_instruction\] | Admin-defined instructions the agent follows | Read, update, create, delete | | Build Agent Skill \[sn_build_agent_skill\] | Skills the agent can use | Read, update, create, delete | | Build Agent Skill Resource \[sn_build_agent_skill_resource\] | Supporting files attached to skills | Read, update, create, delete | | Build Agent User Instruction \[sn_build_agent_user_instruction\] | Personal instructions users give the agent | Read, update, create, delete | | Event telemetry \[sn_build_agent_event_telemetry\] | Usage metrics for individual agent events | Read, update, delete | | Task telemetry \[sn_build_agent_task_telemetry\] | Usage metrics per agent task | Read, update, delete | [Table 7. Main tables for Build Agent] {#ba-properties-installed-with__table_ba-main-tables} ## Access control (ACLs) {#ba-properties-installed-with__ba-access-control} Build Agent (Trial) requires the sn_glider.admin role for every feature, and there is no separate customer role. Some records are also limited to the user who created them. {#ba-properties-installed-with__table_ba-access-levels__entry__3} | Access level | Meaning | Applies to | |-|-|-| | Role only | Any user with sn_glider.admin | Plans, work items, skills, instructions, script requests, file mounts, ATF test results, change logs, activity, task telemetry | | Role and ownership | Role required, and the user must own the record | Conversations, messages, checkpoints | | Hidden | Not visible to customers | Records marked internal, such as Build Agent background runs | [Table 8. Access levels] {#ba-properties-installed-with__table_ba-access-levels} Points to know: * Users with the same role can't see each other's conversations or messages. This is intended. * Admin doesn't bypass ownership on conversations and messages. Even base admin must own the conversation to change it. * Most properties are read and write for the sn_glider.admin role. The prompt-limit properties and tier_override are read-only for admin, so customers can view them but not change them. {#ba-properties-installed-with__ul_rlx_2tl_clc}