Page collection settings

A number of settings can be edited for the page collection, this way:

  1. Edit a page in the publishing app and open the Page menu.

  2. Click the main navigation node for the page collection.

In this example, three page collections has been added in the publishing app, besides Start and News, and “Start” is selected:

../../../_images/page-collection-general-news2.png
  1. Click “Settings”.

../../../_images/page-collection-click-settings-new2.png
  1. Click “Edit” at the bottom to edit the settings.

../../../_images/page-collection-click-edit-new2.png
  1. Use the following settings:

../../../_images/page-collection-settings-612.png

All settings are not shown in the image above, but listed below.

Use the settings this way:

  • Navigation structure/Flat: Select page collection type here; using a navigation structure or flat. If you want to change from navigation structure to flat, you need to first manually flatten the page structure (move sub pages so they all become main pages) and then use the option here.

  • Title: The title for the page collection is shown here. It can be edited if needed. It’s updated everywhere it’s shown when the changes here are published.

  • Layout: Applicable for communities. Here a Layout can be selected. Layouts for communtites works somewhat like page types, but can contain a full set up, ie for several pages. Layouts are created in Omnia admin.

  • Create page dialog: You can set the title for the dialog displayed when an editor has selected to create a new page. If you leave this field blank, the dialog title will be “Create New Page”.

  • Show URL: If the URL for the new page should be shown for the editor when creating a page, select this option. The URL can then be edited.

  • Show properties: If available page properties should be shown for the editor when creating a page, select this option. The properties can then be edited in that stage. Page properties can always be edited after the page has been created.

  • Auto publish: This is a setting probably most relevant for communities. If this option is selected a new page is always published automatically. It’s only applicable when a new page is created, not when it’s updated.

  • Page types: Select which of the page types that should be available for an editor to select when creating a page in this page collection. It can be local page types or tenant page types. Tenant page Types are indicated by the text “(Tenant)”. For more information about tenant page types, see this page: Tenant page types.

  • Automatic page creation: A copy of a page can be published automatically to another page collection or another tenant, when certain rules are met. For more information, see this page: Automatic page creation

  • Promotion channels: You can configure promotion channels to send teasers to Microsoft Teams, Viva Engage, and via Email - for example to use in a publishing campaign. For details, see below.

  • Viva Engage integration: When Viva Engage (former Yammer) integration is setup, a post will be created in the selected Viva Engage community whenever a new page, matching the selected criteria, is created. See below for more information.

  • Taxonomy connection: When this option is activated, it’s possible to connect the page collection to a taxonomy. Whenever a page is created in the page collection, a term will be created in the connected taxonomy and the page will automatically be tagged with the newly created term. This can, for example, be useful in different rollups. For more information, see below.

  • Approval: If approval should be needed for publication of pages (new pages and updates), enable this. If not enabled, editors can publish themselves. See more info about approval settings below.

  • Activities: For a community, activity tracking can be activated. See the heading Settings for activity points on this page, for more information: Setting up a community

  • Notifications: This setting defines when a notification that a page is new should be shown for users, for example in the Notification panel. Normally it’s only when the page is created, not when it’s updated. If this option is activated the page is considered to be new every time it’s updated and a new version is published. Therefore it’s probably more relevant for pages in communities than for publishing pages.

  • Send as Email: Select “Enable send page as Email” if pages in the page collection should be available to send through Email. One example of when this is needed is in a Newsletter inplementation. If this option is activated, authors can decide to send the new or edited page by email, or decide not to, each time the page is published.

  • Scheduling: If scheduling should be available in this page collection, select this option and select the property to be used. The author can then set a scheduled start date and time, using the PROPERTIES tab for the page. Note that scheduled publishing never is mandatory, an author can always choose to publish without using scheduling.

  • Break permission inheritance by default: Select this option if inheritance should be broken when a new page is created within the page collection. This could, for example, be useful for communities. When this option is active, the colleague creating the page will be the page owner, meaning that he or she has full control over who can edit. The new option “Invite co-authors” can then be used to easily add authors for the page, see below.

  • Allow invitation of co-authors: If this option is selected, authors can invite co-authors.

  • Channel: If you enable this, it will be possible for an author to select channels the page should be published to. Publication to a channel may require approval from the channel administrator. See more information below.

  • Open AI: When you activate this option you can set properties for what the Open AI should be able to work with, see below. Also note that two tenant features must be activated for this option to be available and settings for Open AI has to be made in Omnia Admin.

Set default values for a page type

You can set default values for the page types that has been added to the page collection. Any changes you do applies to the active page collection only.

  1. Click the pen for the page type.

../../../_images/page-type-default-pen.png

The default setting is that the settings are inherited from the tenant setting.

  1. Deselect a settings to change it.

../../../_images/page-type-default-deselect.png
  1. Set a new default value for the page type, using the field that becomes available.

../../../_images/page-type-default-setnew.png

Don’t forget to save your changes.

Setup a promotion channel

Do the following to set up a promotion channel:

  1. Click the plus.

  2. Use the following settings:

../../../_images/publishing-channels.png
  • Name: Add a name for the promotion channel here.

  • Posting rule: You can choose that a teaser for a new page in this page collection should always be published in this promotion channel, or you can set up rules for publishing. More information about this below.

  • Type: Can be Microsoft Teams, Viva Engage or Email.

  • Group: Select which group the promotion channel is tied to. If you selected Microsoft Teams, it’s a list of Teams groups and so on.

  • Channel: For a Microsoft Teams group, several Teams channels can exist. Select channel here. (Not available for Viva Engage or Email).

  • Property mapping: The properties used for the teaser are listed here. Map properties you use for these purposes.

  1. To set a posting rule, first select “Only post if”.

  2. Then select property, make other choices if necessary, and click ADD.

../../../_images/promotion-property-add.png

In this simple example, a teaser should only be published to this promotion channel if the news type is Product News.

You can add several posting rules if needed, to further limit what will be published.

(Don’t forget to save when you’re done).

Setup Viva Engage integration for the page collection

The Viva Engage (former Yammer) integration you can set up here is a one way integration; from Omnia to Viva Engage. A prerequisite is that the Feature “Viva Engage integration” is activated in Omnia admin (Tenant level).

To set up Viva Engage integration, do the following:

  1. Select “Edit” to edit the settings.

  2. Click the cogwheel for “Viva Engage integration”.

../../../_images/viva-integration-cogwheel.png
  1. Use these settings:

../../../_images/viva-integration-settings.png
  • Viva Engage group: Select a Viva Engage group to intergrate this page collection with.

  • Initial properties: Select the properties used on pages for Title, Summary and Content.

  • Page creation rule: Select if a Viva Engage post should always be created when a page is added, or only according to certain rules.

  1. Save when you’re done.

To set up rules, do the following:

  1. Select “Only create if*.

  2. Click ADD to add a rule.

  3. Select a property.

../../../_images/viva-integration-property.png
  1. Add settings for that property as needed.

By using settings in the Page likes and comments block, you can set up a two way Viva Engage integration. Note that you must set up the integration here first.

For more information, see: The Page likes and comments block

Allow invitation of co-authors

If “Allow invitation of co-authors” is selected, an author can use this menu option to invite one or more co-authors:

../../../_images/co-author-meny.png

Note that this is not temporary, the co-authors will be added to the page permissions as authors.

For more information about inviting co-authors, see: Invite co-authors

Enable taxonomy connection

When you enable taxonomy connection, select a taxonomy from the list.

../../../_images/page-collection-settings-taxonomy.png

When you have done that every new page in the page collection creates a term in the selected taxonomy, based on the title of the page. The newly created page is automatically tagged with the new term.

Note! If you change a title of a page, the term for the page is NOT changed automatically. If you would like to change the term as well, you have to do that in the term set manually.

Also Note! You must see to that the editors/authors that will create pages in this page collection has permissions to create terms in the selected term set.

Settings for approval

When approval is activated, the following settings are available:

../../../_images/page-collection-approval-settings-v75.png
  • Apply to authors only: If you select this, editors never need approval, they can always publish directly. When an author publishes, approval is needed.

  • Apply to new pages only: When this option is selected, only creating new pages needs approval, not when updating an existing page.

  • Multi step approval: Normally, when this option is not used, only one colleague can approve a page. When this option is used, a number of steps for approval can be set up, meaning several coleagues can need to approve a page. For more information, see below.

When approval is activated, you can select who can approve the creation of a page this way (also used in the multi step approval settings, see below):

  • Anyone - The author can select any colleague as approver when a page is published. See below for more information.

  • Limited list of people - you define the approvers using the field shown (see below). You can define one or more approvers but only one approval is needed each time, from any of the approvers.

  • Based on person property - you select property from the list shown (see below).

  • Term driven: Authors can select approvers from a defined list only. Which approvers will be available depends on the properties selected for the documents. You select the term(s) here. When you have selected one or more terms you can use the cogwheel to set approvers for individual terms in the set.

When “Anyone” is selected the following is shown when an editor sends the page for approval:

../../../_images/approval-anyone-new.png

The author adds the approver to the field “Approver”, types a message and sends the approval request.

When selecting “Limited list of people”, you add approvers by typing their names in the field displayed:

../../../_images/limited-list-new.png

Authors can then only choose between the colleagues in the list when selecting approver.

When you select “Based on person property”, you open the list and select property. Normally just one or two properties are available. Page contact is an example of a field that can be relevant, if such a property is set up.

../../../_images/based-on-person-new.png

Based on person property can result in more colleagues being available for approval. Authors can only choose between these colleagues when selecting approver.

For more information, see this page: Properties

For Term driven, you first select a term, then click the cogwheel.

../../../_images/term-driven-cogwheel.png

Then select the colleague or group that should be available for approval for the term.

In this exeample Robert Johnson is set as approver for all object types (the parent). If you would like to select someone else to be avaialable as approval for, let’s say News article, deselect “Inherit parent settings” and select colleague or group there.

../../../_images/term-driven-cogwheel-approver.png

Setting up multi step approval

When Multi step approval is selected, you set it up this way:

  1. Click ADD STEP and set the following:

../../../_images/multi-step-1-new.png
  1. Add a description of the step in any tenant language.

  2. Select who should be able for approval in this step. See above for information about the options.

  3. Set the following:

  • Use custom message: Use this to customize texts, see below.

  • Allow edit: If this option is selected the “approver” can edit the page with the changes he or she sees as necessary and then approve for publishing, or send back with a comment (if send back is activated for that step).

  • Enable reject: Select this option if publication could be rejected in this step.

  • Enable send back: If it should be possible to send back to previous approval step from here, select this option.

When you select “Use custom message” you can set the following:

../../../_images/multi-step-custom.png

What you can use the fields for should be self explanatory. Also note that you can add button labels, and text for the Email, for different languages by clicking the flag.

  1. Continue adding the needed approval steps the same way.

When you’re finished it can look something like this:

../../../_images/multi-step-2.png

To edit a step, just expand it and use the settings as described above. To adjust the order of the steps, use drag and drop. To delete a step, click the dust bin.

Don’t forget to to publish to save your settings.

Channel settings

When you enable publishing to channels you can also choose that at least one publishing channel is required:

../../../_images/channel-settings.png

I you select this there must be at least one channel selected when a new page is created in the page collection, or the the new page can not be saved.

Options for OpenAI

When activating the OpenAI option, the following settings are available for this page collection:

../../../_images/open-ai-page-collection.png
  • Summary: To activate OpenAI functionality for page summary, select the appropriate summary property here.

  • Text: Likewise for text fields, select property to activate OpenAI functionality.

  • Image: Dall-E is an OpenAI option that can be activated (a feature needs to be activated) and are then available as an image provider in the Image Picker. Select the image property used to activate the functionality.

See the bottom of this page for information about how OpenAI can be used in the RTF editor: Editing text with the RTF Editor

Saving page collection settings

To save the changes to the page collection settings, you need to publish. You can’t save a draft, even if that option is present.