Skip to main content
Strike Graph Basics

Policy Center (Beta)

Learn how to create, manage, and publish internal policies in Strike Graph's Policy Center, and use them as evidence sources and Trust Assets.

Written By Micah

Policy Center gives your team a single place to write, review, and publish the internal policies that your compliance program depends on. Instead of tracking policy documents across shared drives and word processors, you can manage the full lifecycle directly inside Strike Graph: draft content in a rich text editor, publish versioned snapshots, and keep a clear record of who made changes and when.

Published policies can also serve as collection sources for evidence items and back your Trust Assets, so the rest of your compliance program stays connected to the policies it references.

Policy Center is currently in beta. To enable it for your organization, contact your Customer Success Manager.

The policy list

The Policy Center list view shows every policy in your organization. Each row displays the policy's name, status, source, owner, and last modified date.

Use the filters at the top of the list to narrow what you see:

  • Status: Active (the default, which hides archived policies), Draft, Published, or Archived.

  • Owner: filter by a specific team member, or select "No owner" to find unassigned policies.

  • Search: type part of a policy name to find it quickly.

Creating a policy

To create a new policy, click Add policy at the top of the list. You will be prompted for two things:

  • Name: the policy's display name (up to 255 characters).

  • Owner: the person responsible for the policy. This defaults to you, but you can assign someone else.

After you confirm, Strike Graph creates the policy with an empty draft and opens the editor so you can start writing immediately.

The Add policy button is available to users with Manager permissions or above.

Editing a draft

The policy editor gives you a rich text editor to write your policies in. It automatically saves your work as you type, but you can confirm your changes are saved by reviewing the status indicator at the top of the page.

If another team member opens the same draft, the editor shows a presence indicator with their name so you know someone else is working on the policy at the same time. When two people are editing simultaneously, each person's changes are saved independently. If a conflict is detected (someone else saved while you have unsaved changes), a banner appears with a Reload option so you can pull in the latest version. Working on the same policy as the same time as someone else risks losing work, and is not advised.

When you are finished, click Save & close to return to the policy detail page, or click Publish to make the draft the current published version.

Policies you cannot edit in the editor

Some policies cannot be edited directly in the Strike Graph editor:

  • Integration-sourced policies: these are managed by an external system. The editor will direct you to edit the policy at its source.

  • Archived policies: unarchive the policy first to make it editable again.

Publishing

Publishing a policy replaces the current published version with the contents of the draft. The published version is what readers see when they view the policy, and each publish increments the version number. The policy detail page shows the version number, the date it was published, and who published it.

After publishing, Strike Graph generates a PDF of the published version. This PDF is what gets attached when the policy is used as an evidence source.

To publish, you need Manager permissions or above.

Policy details and properties

The policy detail page shows the published version of the policy by default. When the draft has unpublished changes, a toggle lets you switch between the published version and the current draft.

The properties panel on the right side of the page shows:

  • Status: Draft, Published, or Archived.

  • Source: Manual (written in Strike Graph) or the name of the integration that manages it.

  • Owner: the person responsible for the policy.

  • Published version: the current version number.

  • Editors: people who have contributed to the policy.

  • Last modified: when the policy was last changed.

From the detail page, you can also edit the policy's name and owner through Edit details.

Integration-sourced policies

Policies collected from an external integration show the integration's name as their source. These policies update automatically when the integration syncs, and you can trigger a manual sync with the Recollect now button on the detail page.

If a collection fails, an alert appears on the detail page with a link to check the connection in your Integrations settings.

Converting to manual

If you want to stop syncing from the integration and manage a policy directly in Strike Graph, you can convert it to a manual policy. This action is permanent: the policy stops updating from its integration, the draft starts empty, and the published version stays in place until you publish a new one.

If an integration-sourced policy becomes disconnected (the integration source is removed), converting to manual is the path forward for continued management.

Archiving and restoring

Archiving a policy removes it from the active list and prevents further edits. Archived policies are still visible when you apply the Archived status filter.

To restore an archived policy, open it and select Restore. The policy returns to its previous status and becomes editable again.

Using policies as evidence sources

A published policy can serve as the collection source for an evidence item. When you link a policy to evidence, two things happen:

  • The policy's current published version is added to the evidence item immediately.

  • Every future version the policy publishes is added to the evidence item automatically.

This keeps your evidence current without manual re-uploads each time a policy is revised.

To link a policy, open an evidence item's attachment modal and choose the Policy source. Select a published policy from the picker, and the link is created. Each evidence item can be linked to one policy at a time. If you need to change the linked policy, unlink the current one first. Unlinking stops future versions from being added, but attachments that were already added remain on the evidence item.

Linking a policy to evidence requires Contributor permissions or above.

Backing Trust Assets with policies

You can create a Trust Asset that is backed by a published policy. The asset always serves the policy's latest published version, so your Trust Center and any shared Trust Assets stay up to date as policies evolve.

To create a policy-backed Trust Asset, open the Trust Asset Library and choose the Policy source when adding a new asset. Select a published policy, provide a description and effective date, and the asset is created. Each policy can back one Trust Asset.

Activity feed

Policy actions appear in the activity feeds throughout Strike Graph. When a policy is linked to or unlinked from an evidence item, the event is recorded on that evidence item's activity log with a link back to the policy in Policy Center.

Need More Help?

If you have questions about Policy Center or need help getting started, reach out to us through the in-app messenger.