Stages Documentation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
712:cms_sharepoint_online [2025/09/15 14:55] – created - external edit 127.0.0.1712:cms_sharepoint_online [2025/09/16 12:54] (current) – Policnik, Florian
Line 22: Line 22:
 </cms-type> </cms-type>
 </code> </code>
 +
 +
 +===== Features: Download file and open in SharePoint Online  =====
 +
 +This integration provides users with two ways to access a file: Download the file via Stages and open it in SharePoint Online.
 +  * Download via Stages: Stages handles the download for the user. To ensure SharePoint Online file permissions, the user must authenticate via Stages. This behavior can be overwritten by the ''use.system.account.for.download'' setting (see below).
 +  * Open in SharePoint Online: The user is taken to the file in SharePoint Online. User authentication is handled by SharePoint Online. If the link is to the latest version of the file, SharePoint Online will typically offer an editor such as Word Online. If the file in Stages is fixed to a specific revision, SharePoint Online will offer a download or a read-only view of the file. This depends on the file type.
 +
 +The default option is download and can be changed by ''preferred.file.access'' setting (see below).
 +
  
 ===== Host Properties ===== ===== Host Properties =====
Line 68: Line 78:
   * Default Value: Document   * Default Value: Document
   * Description: Name of the **document**  content type. Sharepoint supports multiple content types but stages only supports the default type for documents.   * Description: Name of the **document**  content type. Sharepoint supports multiple content types but stages only supports the default type for documents.
-  * Since Stages 7.5.6.2, 7.6.2.4 and 7.7.0.0 it is possible to define multiple content types. Separate them with a #. For example:+  * It is possible to define multiple content types. Separate them with a #. For example:
  
 <code xml> <code xml>
Line 79: Line 89:
   * Description: The second content type which is supported by stages.   * Description: The second content type which is supported by stages.
   * Known Issue: Typo in Default Value. Has to be Link to a **D**ocument   * Known Issue: Typo in Default Value. Has to be Link to a **D**ocument
-  * Since Stages 7.5.6.2, 7.6.2.4 and 7.7.0.0 it is possible to define multiple link types. Separate them with a #. For example:+  * It is possible to define multiple link types. Separate them with a #. For example:
  
 <code xml> <code xml>
Line 90: Line 100:
   * Description: When set to true, files will be downloaded using the system account.   * Description: When set to true, files will be downloaded using the system account.
  
-> sites.selected.scope (since Stages 7.10.7.0)+ 
 +> preferred.file.access 
 + 
 +  * Default Value: download 
 +  * Description: When set to ''link'', the user will be linked directly to SharePoint Online. The download option can be chosen from the sub-menu. 
 + 
 +> sites.selected.scope
  
   * Default Value: false   * Default Value: false
Line 96: Line 112:
  
  
-==== Proxy configuration (since Stages 7.10.10.0) ====+==== Proxy configuration ====
  
 Stages can communicate with SharePoint Online through a proxy. Fill in the ''proxy.scheme'', ''proxy.hostname'' and ''proxy.port'' host properties to use a proxy. Otherwise no proxy is used. Stages can communicate with SharePoint Online through a proxy. Fill in the ''proxy.scheme'', ''proxy.hostname'' and ''proxy.port'' host properties to use a proxy. Otherwise no proxy is used.
Line 187: Line 203:
 {{ :cms:azure_permissions.png?direct }} {{ :cms:azure_permissions.png?direct }}
  
-=== Recommended option: Application and delegated permission Sites.Selected (Since Stages 7.10.7.0) ===+=== Recommended option: Application and delegated permission Sites.Selected ===
  
 To active this option the setting ''sites.selected.scope'' has to be set to ''true'' in the xml host properties: To active this option the setting ''sites.selected.scope'' has to be set to ''true'' in the xml host properties: