Author: Laiza Tagumpay is a Certified Master Anaplanner with a background in Customer Success and Solution Architecture, now happily building and scaling Anaplan as a CoE Principal Engineer in a biotech company.
As more organizations adopt Anaplan Workflow across multiple teams, it’s helpful to step back and align on how Workflow behaves today, what it does well, and where teams may need to apply additional governance practices.
This post shares observations from hands-on testing, highlights areas teams should be aware of, and suggests practical ways to manage Workflow safely in multi-team tenants while we look forward to continued platform enhancements in the future.
1. Workflow access is tenant-wide
Workflow roles in Anaplan are managed at the tenant level. This means users assigned the Workflow Owner role can see and manage workflow templates across the tenant, regardless of workspace or model boundaries.
This design simplifies administration, but in tenants shared by multiple teams, it’s important to recognize that:
- Workflow visibility is not scoped to a single workspace or model
- There is currently no concept of template-level ownership enforced by the platform
Understanding this behavior early helps teams put the right operational controls in place.
2. Workflow capabilities depend on underlying access
Through testing, we observed that Workflow Owner capabilities vary depending on whether the user has access to the models and UX pages referenced by the workflow.
With access to referenced models and pages, Workflow Owners can:
- Create workflow templates
- Configure and save any workflow tasks
- Start workflow templates
- Delete workflow templates
Without access to referenced models and pages, Workflow Owners can still:
- View workflow templates
- Start workflow templates
- Delete workflow templates
They may attempt to edit workflow templates; however, these configuration changes cannot be saved without access to the underlying components.
Another scenario to be aware of is when a Workflow Owner from one team has access to the models and pages used by another team’s workflow. In this case, the platform does not distinguish “designated” ownership, and the user can still act as a Workflow Owner for that template.
This distinction is important to keep in mind when assigning Workflow Owner roles in shared environments.
3. Observations from audit trail testing
To better understand audit visibility, we ran several test cases. The observations below reflect current platform behavior and are shared for awareness.
Workflow execution
When a workflow is started by someone other than the template creator, the audit log records two entries. WF-1003 shows that the workflow execution started with the template creator id, while WF-1006 identifies the user who initiated the workflow. If you look only at WF-1003, you may misidentify the executor. For governance or audit reviews, always check if there is WF-1006 entry to confirm the true initiator.
Workflow deletion
When a workflow template is deleted, the action is not currently recorded in the tenant audit log.
Workflow editing
- Edit attempts that cannot be saved (due to missing access) are not captured in the audit log.
- Successful edits appear only as a high-level “template updated” event, without details on what changed or who made specific modifications.
These observations highlight the importance of supplementing platform audit logs with internal tracking where required.
4. Why this matters in multi-team tenants
In shared tenants, these behaviors can introduce challenges such as:
- Reduced clarity around who triggered or deleted workflows
- Difficulty reconstructing events during incident reviews
- Additional considerations for regulated or audit-sensitive processes
None of these are blockers to using Workflow — they simply mean teams should be intentional about how Workflow is governed.
5. Practical governance approaches that help today
- Limit workflow owners and require completion of workflow trainings.
- Use naming conventions to clarify ownership, example: [Team] – [Process] – [Purpose] – [Version].
- Maintain a simple workflow registry.
- Prefer versioning over direct edits.
6. Looking ahead
Workflow continues to evolve, and many of the considerations above represent opportunities for future enhancement. In the meantime, being aware of current behavior and adopting a few practical governance habits can help teams confidently scale Workflow across the enterprise.
Key takeaway
Workflow is a powerful capability, and with a small amount of intentional governance, it can be used safely and effectively, even in large, multi-team tenants.
We look forward to continued improvements in this area and would welcome further guidance and enhancements from Anaplan over time.
