Pages

A Page is a governed, authoritative definition of a business concept, such as a critical term, entity, or acronym. Pages are built into the Discover page and organized by domain and subdomain. Each domain and subdomain has its own set of Pages, and users with access to a domain can create and govern them.

Pages are part of Unity Catalog semantics: the business context that you define and govern explicitly, forming the modeled knowledge in Genie Ontology. When Genie One answers a question about a concept you've defined in a Page, it prioritizes the Page's definition over learned knowledge, and cites the Page so users can confirm the source. See How Genie One uses Pages.

To document a single table instead of a concept, use a wiki (Beta).

What's in a Page

A Page contains the following fields:

Field Description
Domain The domain or subdomain the Page belongs to.
Owner The user responsible for the Page. The creator is the owner by default.
Synonyms Alternative names for the concept.
Description A short summary of the concept.
Page body Freeform, rich-text content that supports links, images, tables, and inline @ tagging of Unity Catalog and workspace assets.
Related assets A list of Azure Databricks assets (workspace and Unity Catalog objects) that logically connect to, depend on, or contextualize the Page, such as parent and child Pages, dependent metrics, or associated tables.
Sources A list of Azure Databricks and external assets (workspace and Unity Catalog objects, links) that serve as the origin of the Page content.

An asset can appear under both Related assets and Sources on the same Page.

Example: an Estimates Page

The following example defines an Estimates term in the Financial Data domain. It leads with a precise definition of the concept, explains how the business uses it, and lists examples of its usage.

A Page defining the term "Estimates" in a Financial Data domain, with structured fields followed by Definition, Business use, and Examples sections

Permissions

A Page inherits access from the domain or subdomain it belongs to: anyone who can access the domain can read its published Pages. You don't grant permissions on a Page directly. What a user can do with a domain's Pages depends on their persona:

Persona Access
Consumer Consumers can view, comment on, and suggest edits to published Pages that they don't own. They can also create draft Pages, which only a Page manager or curator can publish. Consumer is the baseline persona for users without any other permissions on the Discover page.
Page owner A user who creates a draft becomes its Page owner. A Page owner can edit their own draft Pages. After a Page manager or curator publishes a consumer's draft, the consumer can no longer edit it, but stays in the Owner field as the point of contact.
Page manager Page managers can edit, publish, unpublish, and delete Pages, accept or reject suggestions, delete comments, and change the Page owner, for any Page in the scope where they hold MANAGE PAGES. In the same scope, they can view all draft Pages. See Grant Page manager permissions.
Curator Curators can do everything a Page manager can do, on any Page in the domains and subdomains where they hold curator permissions (MANAGE DISCOVER at the account level, or MANAGE DOMAIN on a domain or subdomain). Curators can also certify and deprecate Pages. See Curator permissions.

Account admins and workspace admins automatically hold account-level MANAGE DISCOVER and act as curators over every domain and Page. Account admins can grant MANAGE DISCOVER to others at the account level, or MANAGE DOMAIN on a specific domain or subdomain. See Curator permissions.

Grant Page manager permissions

By default, MANAGE PAGES is granted to All account users on every domain, including newly created domains. To limit who can publish and manage Pages in a specific domain and its subdomains, revoke MANAGE PAGES from All account users on that domain and grant it to specific users, groups, or service principals.

Only curators can grant and revoke MANAGE PAGES. A curator with MANAGE DISCOVER can grant or revoke it on any domain or subdomain. A curator with MANAGE DOMAIN can grant or revoke it only on the domains and subdomains where they hold MANAGE DOMAIN. You can grant MANAGE PAGES at three scopes, from broadest to narrowest:

Scope A Page manager with this grant can manage
Account Every Page in every domain and subdomain in the account.
Domain Every Page in the domain and its subdomains.
Subdomain Every Page in the subdomain.

To grant or revoke MANAGE PAGES at the account level:

  1. On the Discover page, click the Kebab menu icon. overflow menu and select Manage Domains.

  2. Click the Permissions tab, then click Grant Permissions.

  3. Select the principal, select Manage Pages under Permissions, and click Save.

    The Grant permissions dialog with Manage Pages selected as the permission

  4. To revoke the permission, click the x on the permission next to the principal.

To grant or revoke MANAGE PAGES on a domain or subdomain:

  1. On the Discover page, open the domain. To scope the grant to a subdomain, open the subdomain from the domain page.
  2. Click the Kebab menu icon. overflow menu and select Domain permissions.
  3. Select the principal, select Manage Pages under Permissions, and click Save.
  4. To revoke the permission, click the x on the permission next to the principal.

Create a Page

Every Page is attached to a domain or subdomain, so you need at least one domain set up before you can create Pages. See Create a domain.

You can author a Page manually or generate one with Genie Code from source material.

Warning

Page data is encrypted at rest with Microsoft-managed keys. Pages don't support customer-managed key (CMK) encryption. Because Pages are an account-level feature, Page data may be replicated globally to support workspaces in different regions. Do not include PII, regulated data, or other sensitive information in Page names, descriptions, synonyms, or body text.

  1. To access Pages, click Discover, then click Pages.

    How to access Pages from the Discover page

  2. Click Create page to open the Page editor.

    The Create page button on the Discover page with the Pages filter applied

  3. Confirm or select the Domain. The domain is filled in automatically if you opened the editor from within a domain, and left empty otherwise.

  4. Add the Page content:

    • To author manually, fill in the structured fields and Page body.
    • To generate the Page with Genie Code, use the Genie Code pane in the Page editor. You can also open the pane from the Discover page or a specific domain page. Attach source material in the pane, which can include external content accessible through MCP connections, public links, files, and Unity Catalog and workspace assets. After Genie Code drafts the structured fields and Page body, attach the appropriate source material under Sources and Related assets.
  5. Save your work as a draft anytime by clicking Save as draft. If you're a Page manager or curator, click Publish to publish the Page. Otherwise, a Page manager or curator publishes your draft. See Edit and publish Pages in draft.

Bulk import Pages

If your organization already documents its terms somewhere else, you can create Pages from those documents instead of writing each one by hand. Genie Code reads the documents you attach, extracts the terms it finds, and returns a set of proposed Pages. You review and edit the proposed Pages before any of them are created.

  1. To access Pages, click Discover, then click Pages.

  2. Click Create page to open the Page editor.

  3. If the Genie Code pane isn't already open, click Sparkle genie code icon. in the upper-right corner of the page to open it.

  4. In the Genie Code pane, click Bulk import pages.

    How to access the Bulk import pages feature from Genie

  5. Follow the prompts. Tell Genie Code which domains you want to add Pages to, and what knowledge sources to use. To attach source material, click Plus icon. in the chat box, then use any of the following:

    • Attach files: Files from your local machine.
    • Add context: Unity Catalog and workspace objects.
    • Connections: External content accessible through MCP connections. You also manage your connections from here.

    You can also paste public links directly into the chat box.

    How to add external sources when bulk importing pages from Genie

  6. Genie Code processes the sources and returns a deduplicated set of proposed Pages for review. You can resolve flags such as conflicts, duplicates, and low-confidence terms, edit the content, and exclude Pages you don't want.

  7. When you finish reviewing, Genie Code creates all of the Pages at once as drafts. You can then review, edit, and publish them under their domains. See Edit and publish Pages in draft.

Edit and publish Pages in draft

The Page owner, a Page manager, or a curator can edit a draft. Only a Page manager or curator can publish it. See Permissions.

  1. Click Discover, then click Pages.

  2. Only published Pages are shown by default. Click Show drafts to view all Pages currently in draft.

    The Show drafts filter applied to the Pages list on the Discover page

  3. Click the Page you want to edit or publish.

  4. Make edits to the Page by clicking Edit, or publish the Page by clicking Publish.

Page managers and curators can unpublish and republish a Page at any time. To unpublish a Page, click the Kebab menu icon. overflow menu on a published Page and select Unpublish.

Collaborate on a Page

Consumers can collaborate on published Pages:

  • Comment: Ask a follow-up question or flag context for the owner. You can edit or delete your own comments. Page managers and curators can delete anyone's comments on a published Page.
  • Suggest edits: Suggest changes to a published Page's body. Each time you click Suggestion, edit the body, and click Save, your edits are grouped into a single batch. There are no inline suggestions. A Page manager or curator accepts or rejects the entire batch at once. Accepting a batch clears every other pending batch on the Page, including batches from other users, and this can't be undone.
  • React: Upvote or downvote a Page to signal whether it answered your question.

Page managers and curators can also edit a published Page's content directly, bypassing the suggestion workflow.

Certify or deprecate a Page

Certify a Page to mark it as an authoritative, trusted definition, or deprecate it to warn users that its content is outdated. Pages use the same system.certification_status system tag as other data assets. See Flag data as certified or deprecated.

To certify or deprecate a Page, you must have curator permissions on its domain or subdomain. See Curator permissions.

  1. Open the Page, click the Kebab menu icon. overflow menu, and select Assign certification.

    The overflow menu on a published Page, with the Assign certification option

  2. Select Certified or Deprecated.

  3. Click Save.

The certified or deprecated icon appears next to the Page name. To change or remove the status, repeat these steps.

How Genie One uses Pages

After you create Pages, Genie One retrieves them and uses the context you defined when it answers questions.

User asking a question in Genie One, which uses Genie Ontology results in its thought process

When a user asks Genie One a question involving a business term or concept you've defined in a Page, Genie One checks Genie Ontology for matching context. It prioritizes the modeled knowledge in your Pages over learned knowledge to generate answers to your questions. Genie One then answers using the Page's definition and surfaces the Page as a citation in its response. Users can click the citation to open the full Page and verify the information.

Sample answer from Genie One citing a Page

Which Pages Genie One can retrieve depends on their state:

  • Published Pages are available in all Genie One conversations.
  • Draft Pages are only available in Genie One conversations with the Page owner.

Manage Pages with the REST API

Create, read, update, delete, and list Pages with the UI or programmatically with the Pages REST API. If your organization maintains many Pages, use the API to manage Pages as code and automate updates.

Each API operation requires the same permissions as the matching operation in the UI. See Permissions. To list Pages, you must have curator permissions for the scope of the request: account-level MANAGE DISCOVER to list Pages across the account, or MANAGE DOMAIN on a domain to list Pages in that domain. Authenticate your requests with a Databricks personal access token for your workspace user or OAuth.

For the list of API operations with the full request and response details, see the Pages REST API reference.

Track Page audit events

Admins can use the audit log system table (system.access.audit) to monitor activity on Pages, such as when users create, update, delete, or view Pages and when they link assets to Pages. Pages events are logged at the account level under the pages service. For the full list of events and their request parameters, see Pages events.

Limitations

  • Pages are available on workspaces with the compliance security profile only when the profile uses the HIPAA, PCI-DSS, C5, TISAX, or HITRUST compliance standard. If your workspace requires any other compliance standard, you can't use Pages on that workspace.
  • Pages don't support customer-managed key (CMK) encryption. See Create a Page.

Pages aren't available in Azure Government regions.