What is your developer-dependent CMS actually costing you? Calculate your costs and get a full report
What is your developer-dependent CMS actually costing you? Calculate your costs and get a full report
Content Operations
For editors whose intranet or portal runs on Microsoft Power Pages: what you change in Agility, how long publishing takes, previewing and editing in context, approvals, and linking to documents in SharePoint.
Your intranet or portal runs on Microsoft Power Pages, and its content comes from Agility. That means you can update news, links and handbook pages yourself, without waiting on IT. This page explains how it works day to day. Your developers set up the connection, described in Microsoft Power Pages.
| You want to change | Where |
|---|---|
| News, announcements, quick links, handbook text, document links, and other content your team set up | Agility |
| Who can see the site and how people sign in | Power Pages (your IT team) |
| Page layout, menus and branding, unless your team modeled them in Agility | Power Pages (your developers) |
| The documents themselves (policies, forms, handbooks) | SharePoint. Agility holds the link |
If you aren't sure whether something is managed in Agility, open the page in Web Studio (below). Anything you can click to edit is managed in Agility.
The site reads content from Agility each time a page loads. There is no export or sync to run.
Saving alone doesn't change the live site. See Previewing, Publishing, and Content States.
Click Preview on a page or item to see your saved changes before anyone else does. The site shows a banner while it's showing unpublished content.
A preview link carries a key that shows unpublished content. Share it only with people who should see drafts, and never in place of publishing.
If a list requires approval, the item stays unpublished until a reviewer approves it, then someone with publish rights publishes it. Items waiting for approval show in preview but not on the live site. See Approvals and Workflows.
Policies, forms and handbooks usually stay in SharePoint, where they keep their versions and permissions. In Agility you add a link to the file:
When the document owner updates the file in SharePoint, the link keeps opening the current version, so you don't need to change anything in Agility. If the file is moved or renamed, update the link.
Don't upload controlled documents to Agility's media library. Files there can be opened by anyone who has the link.
| What you see | What to try |
|---|---|
| My published change isn't on the site | Wait about 30 seconds and refresh. Check that the item is Published, not only saved or awaiting approval |
| The site won't open inside Agility | Your site probably requires sign-in. Use the preview that opens in a new tab |
| A reader says a document link won't open | SharePoint is checking their access. Ask the document owner, or use a link type that covers your whole organization |
| I can't find where something is edited | It may be part of the Power Pages layout. Ask your developers |
