About d.velop contracts for Microsoft 365
Supported browsers
Available languages and language selection
Back
Release and update process
Error messages
Dealing with security vulnerabilities
Changes in Microsoft 365
Logging and monitoring
Isolation in a site collection
Security architecture
Contexts
Data transmission
System requirements
Setting up d.velop contracts for Microsoft 365
Removing d.velop contracts for Microsoft 365
Adding additional fields for all types of contracts
Adding informational text in tooltips
Creating document types
Configuring default values
Configuring the contract status
Configuring the task status
Including additional lists
Configuring the organizational assignment
Calling the administration interface
Start page
Configuring the tabs
Creating and configuring additional contract types
Configuring the search
Configuring permissions
Managing document templates
Enabling links
Enabling signatures
Defining contractual partners management options
Defining e-mail notifications
Creating Power BI reports
Defining buttons
Working with the configuration files
Clearing the cache
Links to the SharePoint administration
Additional document properties in the document area
Managing the technical contact
Automatic status change
Configuring headlines
Configuring the color scheme
Configuring the share feature
Translating additional fields
Terminology memory (expression sets + expressions)
Site content types and columns
Lists and libraries
Globally Unique Identifier for terms
Clearing the cache
Assigning the admin role in Microsoft Entra ID
Reindexing the SharePoint content
Using the correct SharePoint site time zone
Integrating the contracts into the structure
Configuring IDs
What field types are supported in d.velop contracts for Microsoft 365?
Why are changes from SharePoint not displayed in the application?
What types of e-mail notifications can be sent?
What needs to be considered when configuring Sharepoint search?
About d.velop contracts for Microsoft 365
Supported browsers
Available languages and language selection
Release and update process
Error messages
Dealing with security vulnerabilities
Changes in Microsoft 365
Logging and monitoring
Isolation in a site collection
Security architecture
Contexts
Data transmission
System requirements
Setting up d.velop contracts for Microsoft 365
Removing d.velop contracts for Microsoft 365
Adding additional fields for all types of contracts
Adding informational text in tooltips
Creating document types
Configuring default values
Configuring the contract status
Configuring the task status
Including additional lists
Configuring the organizational assignment
Calling the administration interface
Start page
Configuring the tabs
Creating and configuring additional contract types
Configuring the search
Configuring permissions
Managing document templates
Enabling links
Enabling signatures
Defining contractual partners management options
Defining e-mail notifications
Creating Power BI reports
Defining buttons
Working with the configuration files
Clearing the cache
Links to the SharePoint administration
Additional document properties in the document area
Managing the technical contact
Automatic status change
Configuring headlines
Configuring the color scheme
Configuring the share feature
Translating additional fields
Terminology memory (expression sets + expressions)
Site content types and columns
Lists and libraries
Globally Unique Identifier for terms
Clearing the cache
Assigning the admin role in Microsoft Entra ID
Reindexing the SharePoint content
Using the correct SharePoint site time zone
Integrating the contracts into the structure
Configuring IDs
What field types are supported in d.velop contracts for Microsoft 365?
Why are changes from SharePoint not displayed in the application?
What types of e-mail notifications can be sent?
What needs to be considered when configuring Sharepoint search?
Open Documentation Menu
Using the correct SharePoint site time zone
The correct setting of the time zone in the SharePoint site is an important part for the stable operation of the d.velop contracts for Microsoft 365 installation.
Please note that dates are stored and displayed in the same way regardless of the user's time zone. If a user in a different time zone maintains a date, all users will see exactly this date, even if they are in a different time zone.
Warning
The time zone must not be changed subsequently, otherwise existing runtime data (e.g. the start of the contract) may change.