Skip to main content

Change Requests

Change requests enable governed modifications to data products. Unlike access requests (which control who can use data), change requests control what changes can be made to a product's configuration, metadata, or structure.

What is a Change Request?​

A Change Request is a formal proposal to modify a data product. Changes might include updating metadata or descriptions, modifying quality check configurations, reclassifying risk levels, changing governance assignments, or altering technical properties such as schema definitions.

Rather than allowing any user to make changes directly, the change request system routes proposed modifications through an approval workflow. This ensures that changes are reviewed by the appropriate stakeholders — typically the Data Architect and Product Owner — before being applied.

Creating a Change Request​

From a Product​

Navigate to the data product you want to modify. Click Request Change to open the change request form. Describe the proposed change, provide a business justification, and submit the request.

Survey Forms​

Some products are configured with survey templates that structure the change request process. When a survey is attached to a product's change request flow, the submission form includes additional structured fields (such as dropdowns, checkboxes, or text inputs) that capture specific information required for review. This ensures that reviewers receive consistent, complete information with every request.

tip

Survey templates are configured at the product level by space administrators. See Survey Templates for details on setting these up.

Request Lifecycle​

States​

A change request moves through the following states:

  • Pending — The request has been submitted and is awaiting review
  • Approved — The request has been approved by all required reviewers
  • Rejected — The request has been denied, with reviewer notes explaining why
  • Completed — The approved changes have been applied to the product

Workflow Integration​

When a product has an active Change Request workflow configured, submitting a change request automatically triggers that workflow. The request flows through the defined approval steps — for example, first to the Data Architect for technical review, then to the Product Owner for business approval.

If no workflow is configured, the request remains in Pending status for manual review by space administrators.

Reviewing Change Requests​

For Approvers​

When a change request is assigned to you for review, you will see the proposed changes and justification, any survey responses submitted by the requester, the product's current state, and the workflow context. You can Approve or Reject the request, with optional notes explaining your decision.

Request List​

View all change requests for a product in the product's Requests tab. Administrators can also view change requests across the space using the requests management page. Filter by status to focus on pending reviews.

Commenting​

Change requests support threaded discussions. Both the requester and reviewers can add comments to ask questions, provide additional context, or discuss the proposed changes before a decision is made.

Revocation Requests​

In addition to change requests, users can submit Revocation Requests to voluntarily relinquish their own access to a data product. This is useful when a project concludes or when a user no longer needs access to specific data. Revocation requests follow a simplified approval flow and are tracked for audit purposes.

Audit Trail​

Every change request is fully audited. The system records who submitted the request, the proposed changes, all approval or rejection decisions with timestamps, any comments or discussions, and the final outcome. This history is available for compliance reviews, governance meetings, and regulatory audits.

Learn More​