The simple way to run a Salesforce Center of Excellence

Roles and permissions

Decide who on your team can see, approve and deploy changes, then give each person only the access they need.

In Blue Canvas you set roles and permissions for your team, with authentication for each user. A CoE can keep production access small while letting everyone build in sandboxes.

Approval workflows

Every change gets reviewed and approved before it goes live. No exceptions.

Blue Canvas lets you require release approvals, so a deployment cannot reach production until the right person signs off. This gives the CoE a clear record of who approved what.

Deployment rules

Write down who can promote changes, and to which orgs. Then enforce it in the tool, not just in a document.

Deployment permission rules in Blue Canvas control who can deploy to which org. For example, developers can deploy to UAT, but only release managers can deploy to production.

Defining your path to production

Pick one fixed route that every change follows, for example dev sandbox, UAT sandbox, then production.

When every team uses the same path, testing always happens in the same place and nothing skips a step. In Blue Canvas you connect your orgs and move changes along this path.

Org compare and deploy

Compare two orgs to see exactly what is different, then select the changes you want to deploy.

Blue Canvas shows the differences between orgs side by side, so you deploy only what you choose instead of moving everything.

Releasing multiple features in bulk

Group several finished features into one release instead of deploying them one by one.

Bulk releases in Blue Canvas let you ship many changes together, which makes release days predictable and easier to communicate to the business.

Continuous integration

Continuous integration checks changes automatically as they are ready, so problems show up early.

CI is included in the Blue Canvas plan. It runs validation and tests on your changes before they move forward, without a separate tool.

Manual steps and Jira links

Some release work happens outside Salesforce. Track it next to the deployment so nothing is forgotten.

Blue Canvas lets you track manual steps and link deployments to Jira issues, so the release record covers both the metadata and the tasks around it.

Code review and feedback

A second pair of eyes on every change catches mistakes before they reach production.

Blue Canvas supports peer review on deployment requests, so reviewers can see the changes and give feedback in the same place the release happens.

Code quality and testing

Set a quality bar and check every change against it, including running tests before release.

Blue Canvas runs automated validation and testing on your deployment package, so broken or low-quality changes are flagged before they ship.

Merge conflicts

When two people change the same thing, one change can overwrite the other. Resolve conflicts before deploying.

Blue Canvas detects merge conflicts and helps you resolve them, so teams working in parallel do not lose each other's work.

Dependencies

Salesforce metadata depends on other metadata. Deploying one piece without the pieces it needs breaks the release.

Blue Canvas checks dependencies before you deploy, so the components your change relies on come along with it.

Audit trail in Git

Every change is recorded in Git: who made it, what changed and when.

Because Blue Canvas versions your metadata in Git, the CoE always has a complete history to answer audit questions without digging through setup audit trails by hand.

SOC 2 and security controls

Your release process is only as trustworthy as the platform behind it.

Blue Canvas is SOC 2 certified and includes security controls like roles, permissions and authentication, which helps the CoE meet internal security requirements.

Metadata backups

Back up your metadata automatically so you can recover from mistakes or data loss.

Blue Canvas backs up your org metadata, giving the CoE a safety net that does not depend on anyone remembering to run an export.

One-click rollback

When a release causes a problem, undo it fast instead of fixing it live in production.

Blue Canvas offers one-click rollback, so you can restore the previous state while you fix the issue properly in a sandbox.

Spotting org drift

Orgs drift apart when people make changes directly in production or forget to back-promote. Compare orgs regularly to catch it.

Blue Canvas org comparison shows the differences between your orgs, so the CoE can spot drift early and bring environments back in line.

For admins

Admins should not need to learn Git or the command line to follow the release process.

Blue Canvas gives admins a visual interface to compare orgs, select changes and deploy, so they follow the same governed process as developers.

For developers

Developers can keep the tools they already like, including Git.

Blue Canvas integrates with Git, so developers can work with branches and pull requests while staying inside the same release process as everyone else.

For partners and consultants

External partners should follow the same process as your internal team, not a side channel.

Because Blue Canvas uses one platform with roles and permissions, you can give partners access to the orgs they need while keeping the same reviews and approvals in place.

Onboarding new team members

A new team member should be able to learn the release process in days, not months.

When the whole process lives in one tool with one path to production, onboarding is mostly showing someone the steps once. A CoE with a documented, tool-enforced process spends less time training and retraining.

Tracking Agentforce metadata

Agentforce agents are Salesforce metadata, so they belong in version control like everything else.

Blue Canvas tracks Agentforce metadata changes in Git, giving the CoE a history of how each agent changed over time.

Testing agent changes in sandboxes

Build and test agent changes in a sandbox first, never directly in production.

With Blue Canvas you can compare agent changes between orgs and promote them through the same dev, UAT and production path as other metadata.

Learn more: Trust Your Agents (Trailhead)

Approvals for AI changes

AI changes deserve the same sign-off as any other change, maybe more.

The same release approvals in Blue Canvas apply to Agentforce changes, so an agent update cannot go live without the right person approving it.

Rolling back AI changes

If an agent behaves badly after a release, roll it back to the last known good version.

Blue Canvas one-click rollback works for Agentforce metadata too, so the CoE can undo a problematic AI change quickly.