Chronicle Watch the 50-second tour Book a walkthrough
Book a walkthrough Tour

Questions and answers

What people ask us about Chronicle

Straight answers to the questions internal communications, authors, approvers and IT raise most often.

About Chronicle

What is Chronicle?

Chronicle by iomer is a news centre for SharePoint. Everyone gets one place for the organization’s news: featured stories, the latest news, topics, search and an archive. Authors write from templates, the right people approve with every edit marked, and news owners decide what’s featured and when old news comes down. Each story is a SharePoint news page.

We already use SharePoint news.

Keep using it: every Chronicle story is still a SharePoint news page, so it shows in SharePoint news like any other. Chronicle adds what SharePoint news leaves to you: templates, approval routes with edits marked, a news centre with featuring, topics and search, and archive and delete dates on every story.

Why not an employee communications platform?

If you want a separate app for staff without Microsoft 365 accounts, or email and push campaigns in one tool, a dedicated platform may suit you better, and we’ll say so. If you want news that lives on your own SharePoint intranet, uses the sign-in your people already have, and stays under your own retention and residency settings, Chronicle is built for that.

Our intranet already has a news page.

Show us. If it covers what you need, keep it. Chronicle adds templates, approval workflows with tracked edits, featuring and archive rules, and twelve news web parts that can sit on your existing intranet pages.

How is Chronicle different from Hazel?

They’re related, not the same. Hazel is a searchable knowledge centre for large libraries of procedures, job aids and guides that people look up and follow. Chronicle is for news: stories with a publish date, written from templates, approved, featured for a time and then archived. Many organizations keep procedures in Hazel and news in Chronicle.

Is Chronicle a product or a custom build?

Neither. Chronicle is a solution accelerator. The news centre, the designer and templates, approvals with tracked edits, featuring, archive and retire rules, the news web parts and the audit log are already built and the same for every organization, so you don’t pay for a build from scratch. iomer then builds your organization’s version as a single deployment package, with your brand, templates, approval routes and archive rules, and installs it in your tenant. It’s part of iomer Solution Accelerators for SharePoint.

Who installs Chronicle?

iomer does. We build a single deployment package for your organization and install it on your news site with your Microsoft 365 admin, who approves the two delegated permissions once. A site owner runs the guided setup with us. If you use the flows, we set them up under a service account you provide. There’s nothing for your IT team to assemble.

How different can our version be from another organization’s?

Different where it matters to you: your news brand, templates, topics and departments, your approval workflows and the rules that route news to them, who can write for which department, your archive and delete periods, and which news web parts go where. The foundation underneath (the web part, the list design, the permission design, the two Graph permissions and the flows) works the same way in every build. That’s deliberate: it’s already built, and it’s what your IT team reviews.

What happens when we need changes?

Your administrators add and change topics, departments, leads, templates, workflows, routing rules, archive rules and the news brand in Chronicle’s Administration. They’re data, so they don’t need a release. Changes to the web part itself come as a new version of your package, built, tested and installed by iomer.

Writing, approving and publishing

How does an author write a story?

They start from a template, so the designer opens with the layout and sample text in place. Blocks are dragged in or selected, the page saves as they work, and a Before you publish checklist flags anything left: sample text not replaced, a missing summary, or an image without a description. The approval route shows before they submit.

Can approvers change the story, or only comment?

Both, when the workflow step allows edits. An approver selects Edit the draft and changes it in the designer. Every change is tracked word by word against what the author submitted, so the author sees added words in green and removed words struck through. The author can accept the edits and publish at once, or make more changes, which sends the news through approval again from the first step.

How does Chronicle know who should approve a story?

Routing rules, checked top to bottom. The first rule that matches the story’s template, department, topic, series or campaign picks the workflow, and the workflow names each step’s approvers: the author’s manager, a department or topic lead, a campaign owner, the site approvers or a named person.

Do approvers need a licence or a role?

No extra licence: approvers use the Microsoft 365 account they already have. Someone a workflow names, such as a department lead or the author’s manager, doesn’t need Chronicle’s Approver role, but they must be in the Chronicle Approvers group to open drafts. Chronicle warns the author before submitting if someone on the route isn’t.

Can we schedule news to publish later?

Yes, when the Publish and lifecycle flow is set up. The author sets a date and time under Details, and the story goes live within the hour after it. Without the flow, news publishes as soon as it’s approved.

What about our existing news?

Your existing SharePoint news pages stay where they are; Chronicle doesn’t import them. In planning we look at them with you and agree which to leave as they are, which to take down, and whether any recent stories should be rewritten in Chronicle so they carry its topics and archive dates.

Records and compliance

Does Chronicle make us compliant?

No tool does that on its own. Chronicle supports your communications and records policies by keeping the record of what was published: who wrote each story, who approved it at each step and what they changed, when it was published and archived, and an audit log that Chronicle never edits or deletes.

Can we show who approved a story, and what they changed?

Yes. Each story’s history shows who submitted it, who approved it or sent it back at each step, with their comments, and when it was published. Approvers’ edits are kept against the version the author submitted. Auditors can read all of it and export the audit log to CSV.

What happens to news once it’s out of date?

Every story gets an archive date and, once archived, a delete date, from your defaults or a rule by topic, series, template or campaign. Archived stories leave the featured area and SharePoint news feeds, and stay searchable if you allow it. Retired pages go to the site recycle bin. The Publish and lifecycle flow does this on the dates; without it, owners do it by hand.

Who can see who liked a story?

Chronicle’s screens show totals only. Reactions and saved stories are stored in each person’s name in a SharePoint list everyone on the site can read, so someone who opens that list can see who reacted. If that’s a concern, turn off reactions and save for later.

IT and licensing

Where is our data stored?

In SharePoint lists on your news site and one SharePoint news page per published story, in your own Microsoft 365 tenant, under your existing security, retention and data residency settings. Pictures authors upload go to the site’s Site Assets library. If you use the flows, their run history lives in your Power Platform environment. iomer holds none of your data.

Is any of our data stored outside Microsoft 365?

No. Chronicle has no separate database, server or vendor cloud, and sends nothing outside your tenant. The one outside request is for font files from Google Fonts, for the news brand’s display fonts; no personal data goes with it. If you share campaigns with Herald, they sit in a list on a SharePoint site in your tenant.

What licences do we need?

Microsoft 365 with SharePoint Online, and an account for everyone who reads or writes the news. Authors and approvers need nothing extra. The two Power Automate flows, if you use them, run as a service account with a Microsoft 365 licence that includes Exchange Online and Power Automate. They use only the standard SharePoint and Office 365 Outlook connectors, so no premium Power Automate licence is needed. See Platform and IT for details.

Which permissions does Chronicle need?

Two Microsoft Graph permissions, both delegated: User.Read.All, for people pickers, job titles, departments and the author’s manager for manager approvals; and GroupMember.Read.All, so roles given to an Entra ID group apply to its members. Chronicle reads the directory as the person using it and never writes to it. A SharePoint administrator approves them once on the API access page.

Do we have to use Power Automate?

No. Without the flows Chronicle works on demand: approvers see waiting news under Approvals, news publishes when it’s approved, and owners archive and retire stories by hand from what’s due. Chronicle’s screens say so. The two flows add emails to approvers and authors, scheduled publishing, archiving and retiring on their dates, and reminders before a story archives. They run as a service account you provide, and switching one off in Chronicle stops it.

Will our news show in search and Copilot?

Published stories are SharePoint news pages, so Microsoft 365 search and Copilot treat them like any other content people can open, and people only find what they can open. Drafts and approvals are for Chronicle’s own groups, and its guides say which of its other lists to take out of search.

Will Microsoft 365 updates break Chronicle?

Chronicle uses supported Microsoft interfaces: the SharePoint Framework, SharePoint lists and pages, delegated Microsoft Graph and Power Automate. If a Microsoft change ever does affect it, iomer builds and installs a new version of your package. The guided setup adds any new columns or lists, and nothing is renamed or removed.

How would we remove Chronicle?

Turn off both flow switches in Chronicle and the flows themselves, then remove the apps. The lists, news pages and their data stay in your tenant until a site owner deletes them. Microsoft doesn’t remove a Graph permission approval when a solution is removed, so your administrator removes it separately if you want it gone.

Buying Chronicle

How much does Chronicle cost?

It depends on how many templates, workflows and routing rules you need, whether you want the flows, and how much help you want with launch, so we scope it with you first. Once we’ve been through your requirements, we give you a work estimate and a written proposal. Chronicle runs on the Microsoft 365 you already have. How pricing works.

Who supports Chronicle after launch?

iomer supports and extends it after launch: new templates and workflows, changes and support. How support is packaged is set out in your proposal.

Does Chronicle work with Hazel, Beacon and Journey?

Chronicle, Hazel for procedures, Beacon for policy sign-off and Journey for onboarding are built the same way and delivered by the same iomer team, so a customer running one already has the site, the skills and the governance model for the next. A story can link to a Hazel article or a Beacon policy like any other page. If you also use Herald, iomer’s newsletter accelerator, Chronicle can suggest a published story to a newsletter and share campaigns with it.

Can we see Chronicle before we decide?

Yes. Watch the 50-second tour now, with no sign-up, or book a 30-minute walkthrough set up with topics and routes like yours.

Is there a datasheet I can share?

Yes. Download the two-page datasheet or the four-page brochure. Both are PDFs with no form to fill in.

Is Chronicle right for us?

A good fit, and when it isn’t

Chronicle fits well when you

  • Use Microsoft 365, with SharePoint Online as your intranet
  • Have news coming from several departments, locations or leaders, with no common process
  • Want approvals that reach the right people, with edits visible
  • Have, or will name, an owner for the news centre
  • Want your news and its records to stay in your own tenant

Something else may suit you better if you

  • Want a separate employee app, with push notifications, for staff without Microsoft 365 accounts
  • Run on Google Workspace or Slack
  • Have one person writing all the news, where SharePoint’s own news may already do the job
  • Need a public newsroom or press site for outside readers
  • Mainly want email newsletters, which is Herald’s job

Still have a question?

Watch the 50-second tour, ask us in a 30-minute walkthrough, or call 780.424.3122.