Saved changes are drafts. The board sees them only once they are published, so a half-finished decision is never read as a real one. Portfolio Editors and Administrators publish. Publishing releases your own staged changes, not anyone else's.
Publish
- On the control page, find Publish to the board view. Staged now lists each project's waiting changes and who made them.
- Choose the button that counts your changes, such as Publish 3 changes to the board view. If you have none it says Nothing of yours to publish.
- Check the summary and confirm with Publish 3 changes (your number).
The change log records a Published entry, and Board Members and Auditors are told the board view has been updated.
When publishing is blocked
If another editor also has unpublished changes on one of the same projects, Publishing is blocked for now opens and names them. Publishing would release their work unseen. Ask them to publish theirs first, then publish yours.
When a second person must approve
A release that changes approved budgets by more than the threshold in the settings needs another Portfolio Editor or Administrator. Publish: a second person must approve shows the budgets before and after.
- The other person types their Approver's sign-in (email or user name) and Their password.
- Choose Approve and publish.
Their sign-in goes straight to Core's front door, which confirms them; Project Tracker never sees or keeps the password. In the sandbox, another demo persona with a portfolio role, such as the supervisor, can approve.
Changes to the portfolio details are staged and published the same way.