The report type determines who can see the report and who can manage it.

The simplest way to think about them is:

Your GUIDEcx role determines which of these reports you can view or create.

Standard reports are created and maintained by GUIDEcx.

They provide ready-to-use reporting for common onboarding, Professional Services, customer engagement, project management, time, and operational questions.

Examples include:

Standard reports can be viewed by Admins, Managers, Guides, Task Owners, and Contributors.

They are not editable custom reports.

If you're not sure which standard report to use, see the GUIDEreports overview.

A Personal report is a custom GUIDEreport that belongs to the person who created it.

Only the report owner can view and manage it.

Personal reports are useful when you want to:

Admins and Managers can create Personal reports.

The owner can edit or delete their Personal reports.

Because Personal reports are private, other users — including other Admins — cannot use them as shared workspace reporting.

A Workspace report is a custom report shared with your internal GUIDEcx team.

Workspace reports can be viewed by:

Only Admins can create and publish Workspace reports.

An Admin can also edit or delete the Workspace reports they own.

Workspace visibility applies to the internal workspace as a whole. You cannot currently make a Workspace report visible to only a selected group of internal users.

Observers do not have access to GUIDEreports.

Your workspace role determines what you can do with reports.

Personal reports remain visible only to the person who created them, so a user does not gain access to someone else's Personal report simply because they have an Admin or Manager role.

If you're creating a custom report, your intended audience should guide which type you choose.

You are building something for your own use.

For example, a Manager might create a Personal report that helps answer:

“Which customer-owned tasks do I want to review before my portfolio meeting?”

That report can remain private because it supports that Manager's personal workflow.

The report should become a shared reporting resource for your internal team.

For example, an Admin might create a Workspace report for a weekly leadership review that answers:

“Which enterprise implementations are currently late or forecasted late?”

Because the report supports a shared operating process, making it available across the workspace makes more sense.

Note: Only Admins can create Workspace reports.

An Admin who owns a custom report can change its visibility between Personal and Workspace.

This can be useful when a report begins as an experiment and later becomes valuable to the broader team.

For example:

The reverse can also be useful if a shared report no longer needs to be available across the workspace.

Managers cannot publish Workspace reports, so their custom reports remain Personal.

Having an Admin role does not give you editing access to every custom report created by another Admin.

If another Admin creates a Workspace report, you can view the report as part of the workspace, but you cannot edit that Admin's report or save a copy of it for yourself.

This means teams may want to consider report ownership when creating dashboards that will become part of an ongoing reporting process.

For example, if a report will be used in a recurring company-wide delivery review, decide which Admin should own and maintain that report.

This is a suggested team practice rather than a product requirement.

The GUIDEreports interface can sometimes show report-management controls to users who do not have permission to complete those actions.

For example:

These controls do not override your GUIDEcx permissions.

If you do not have permission to perform the action, GUIDEcx prevents the change from being saved and may display a Failed to Save Changes error.

Important: Seeing an editing control does not necessarily mean your role has permission to use it. The permission table in this article reflects what each role can successfully do.

The following is an illustrative Professional Services scenario.

A delivery team wants a dashboard for its Monday morning portfolio review.

A Manager first creates a Personal report to experiment with the metrics they want to review.

After testing it, the team decides the dashboard should become a shared resource.

Because Managers cannot publish Workspace reports, an Admin creates or maintains the shared Workspace version for the team.

Now:

The team gets a shared reporting experience without giving every viewer permission to change the report.

These are suggested reporting practices rather than product requirements.

If you're still deciding which widgets belong on a custom report, a Personal report gives you space to refine the idea before making it part of your team's shared reporting experience.

If multiple people need the same dashboard for a recurring portfolio review, customer health review, or operational meeting, consider creating a Workspace report.

This helps everyone work from the same reporting view.

Because another Admin cannot edit or copy an Admin's report, consider who should own important shared reports before they become part of an ongoing team process.

A title like Enterprise Implementation Health or Weekly Customer Action Review makes it easier for other users to understand why the report exists.

A Workspace report can be visible to many internal users without giving those users permission to change it.

This makes Workspace reports useful for distributing a consistent reporting view.

A Personal report is visible only to its owner.

A Workspace report is visible to internal users who have GUIDEreports access.

Admins and Managers can create Personal reports. Only Admins can create Workspace reports.

No.

Managers can create and manage Personal reports, but they cannot successfully publish a Workspace report.

The interface may display a Workspace publishing option, but the Manager's role does not have permission to complete that action.

Managers cannot change their reports to Workspace visibility.

Workspace reports can only be created or published by Admins.

Yes.

An Admin who owns the report can change its visibility between Personal and Workspace.

This is useful when a report starts as an experiment and later becomes valuable to the broader team.

No.

Other Admins can view a Workspace report, but they cannot edit a custom report owned by another Admin.

No.

Admins cannot currently save a copy of another Admin's report for themselves.

No.

Guides can view Standard and Workspace reports but cannot create, edit, or delete reports.

Task Owners and Contributors can view Standard and Workspace reports.

They cannot create, edit, or delete reports.

Some GUIDEreports controls may still appear in the interface even when your role does not have permission to complete the action.

GUIDEcx will prevent the unauthorized change from being saved and may display a Failed to Save Changes error.

Use your GUIDEcx role — rather than the presence of an on-screen control — to determine which actions are available to you.

One possible reason is that your role does not have permission to perform the report-management action you selected.

For example:

Check the permissions table in this article to confirm whether your role supports the action.

No.

Workspace report visibility is not currently configurable by individual user or group.

A Workspace report is available to internal users who have permission to view Workspace reports.

If a report should remain private, use a Personal report instead.

No.

Observers do not have access to GUIDEreports.

Standard reports are created and maintained by GUIDEcx rather than individual workspace users.

If you need a different reporting view, consider creating a custom report instead of changing the Standard report.

Your Manager role lets you create and manage your own Personal reports.

A Workspace report created by an Admin is shared for viewing, but viewing a shared report does not give you permission to edit it.

Custom-report ownership still applies to Admins.

You can manage the Personal and Workspace reports you own, but another Admin's report remains managed by its owner.

Start with a Personal report.

Once the report is useful and repeatable, an Admin can decide whether it should become a Workspace report for the broader team.

Use these resources depending on what you want to do next: