Administrator Guide

Foreword

The following instructions are based on the assumption that SalesTim Automation is already installed. If SalesTim Automation is not installed yet, please refer to the following document to install and configure SalesTim Automation:

Access and Login to SalesTim Automation?

Please refer to the User Guide / Access SalesTim Automation

"Settings" Dashboard

By default, SalesTim Automation redirects you to the "My Requests" dashboard.
If you're a member of the Office 365 global administrators group, you can access the "Settings" dashboard from the main menu:

requests

From there, you can access the 3 main settings area of SalesTim Automation:

  • "Templates Catalog"
  • "Service Account"
  • "Advanced Customization"

requests

Keep in mind that in addition to the "My Requests" and "Settings" menu item, if you're a member of an approval team, you will also see the "Approval" menu item.

Templates Catalog

View your templates

The template catalog tab is the main one, where you can manage your corporate catalog of teams templates. These templates enables you to enforce your conventions and policies across your company, and will be available to users during when requesting a new team.

The main view consists of your existing templates:

requests

You can sort your templates for an easier navigation by clicking on the columns headers, or search for them from the search box in the top right of the templates catalog.

During setup, a "Default team" template has been provisioned. This template will create a new team using the Microsoft Teams blank template.

Default Template

You cannot delete the "Default team" template.
If you don't want to use it, just disable it from the main "Information" tab.

Manage your templates

To create a new template, select "Create a new team template".
N.B : To edit an existing template, just click on its name from the list. The edit form is similar to the creation form.

Template Information

The "Information" tab defines the main characteristics and settings of your template:

requests

The following settings are available:

  • Select an existing team as a template: Mandatory. Search for an existing team that will be cloned to create the new team. This team is thereafter refered as the "original team"
  • Template availability for end-users: Defines if a template is enabled or disabled, meaning if it will be shown to end-users when requesting a new team
  • Template name and description: These information are showned to end-user during the selection of their template
  • What you'd like to include from the original team: The different characteristics that will be cloned from the "original team" to the new one. You can selectively enable or disable these characteristics among:
    • Apps: The apps installed in the "original team"
    • Tabs: The tabs added in the "original team"
    • Settings: The team settings configured in the "original team"
    • Channels: The channels created in the "original team"
    • Members: The owners and members in the "original team"
  • Team name, description and welcome message default values

Email generation Remove non alpha-numeric characters except - and _ Replace - and _ by a space Apply Camel-case Remove Space

Template Naming Conventions

Prefix-suffix naming policy Fixed strings

Request information

request.team.name request.team.description request.team.welcomeMessage request.template.name request.requester.name request.requester.email

Azure Active Directory attributes, including:

msDisplayName msUPN msEmail msPreferredLanguage msGivenName msCountry msCompanyName msDepartment msCity msJobTitle msSurname msUsageLocation

Team naming conventions

" * : < > ? / \ | The total prefix/suffix + string length is restricted to 53 characters

Custom blocked words The blocked words are case-insensitive. When a user enters a blocked word, the group client will show an error message with the blocked word. There are no character restrictions in the blocked words used. There is an upper limit of 5000 words that can be set as blocked words.

Team Membership

If you enabled the "Members" cloning option, the members from the original team will be "added" to the members specified by the requester during its request.

Template Approval Policy

The "Approval" tab defines the main approval settings of your template:

requests

The following settings are available:

  • Moderation settings: Enable or disable approval for this template
  • Approval Team: Search for users from your corporate directory to add them to the approval team for this template.

Approval Team Onboarding

Members from the approval team will receive email notifications as part of the approval process for requests related to this template.
Don't forget to send the Approver Guide before!

Template Security Policy

The "Security & Privacy" tab defines the main security and privacy policy of your template:

requests

The following settings are available:

  • Team Privacy: "Private" by default. Defines if the new team will be created as:
    • "Private": Meaning that only team owners will be able to add members
    • "Public" Meaning that anyone in your organization will be able to join the team without validation
  • Team Membership: "Enabled" by default. Choose if the requester is automatically added as a team owner, or only as a member.

Requester as an owner

Disabling this option may result in a deceptive user experience, as the requester will expect to be able to manage its own team by itself

  • Permanent Owners and Members: Search for users from your corporate directory to systematically add them as owners or members of teams created using this template

Team Membership

Permament owners and members will be "added" to the members specified by the requester during its request.

Template Adoption Plan

The "Adoption" tab allows you to defines the content of 3 emails to be sent:

  • At the creation of the team
  • One week later
  • two weeks later

requests

Adoption Plan Emails

These emails will be sent to owners each time a new team is created with this template.

Service Account

From the "Service Account" tab, you can define the Office 365 account that will execute the different operations, such as new teams provisioning.

requests

Security Best Practice

By default, SalesTim Automation will use the account you've used during the "Admin Consent" step as its main service account for background processing.
THIS IS NOT A BEST PRACTICE AND YOU SHOULD NOT USE THIS DEFAULT CONFIGURATION IN PRODUCTION ENVIRONMENTS.

To configure the service account to be used, select the "SIGN IN" button, and log in with it's credentials.

Service Account Minimal Security

The service account must at least have the following Microsoft Graph permissions:

  • profile
  • offline_access
  • User.Read
  • Mail.Send
  • Group.ReadWrite.All
  • User.Read.All
  • Directory.AccessAsUser.All
  • Directory.Read.All

Please refer to the Microsoft Graph Permissions Reference for further information about Microsoft Graph permissions.

Advanced Customization

From the "Advanced Configuration" tab, you can inject custom JS and CSS code to the "New team request" form.

requests

Javascript

Don't include your code between script tags
Just include your js code directly:

console.log('Hello World');