Modifying a Tab/Team/Channel/Site

Required?

Job

Specifies the job to create or modify

String E.g Create Site, Create Channel

Required

clientid

Specify the client id

Integer - 44322

Required

matterid

Specify matter id

Integer - 44322

Required

ClientName

Specify the client name

String - ClientTest

Required

MatterName

Specify the matter name

String - MatterTest

Required

WorkspaceName

Specify Tab name

String - Tab Testing

Required

CreateInOffice365

Create this in Office 365, or not. Setting is used for the ETL creation and move of Teams to DMS.

Number- 1 to create, 0 to skip

Required

CreateInImanage

Creates in iManage

Number- 1 to create, 0 to skip

Required

CreateinNetDocuments

Creates in NetDocuments

Number- 1 to create, 0 to skip

Required

Office365Group

Specify the name of Office365 Group

String- GroupNew543211

Optional

mailnickname

Specify nickname for mailing. The same as Office365Group typically.

String; GroupNew543211

Optional

Office365Type

Specify the type of Office 365 object being managed. This can be group, teams, channels, tabs, site.

String: Tab

Channel

Teams

Site

Required

Url

URL of the website for the Office 365 object

String: https://y*****be.com

Optional

ContentUrl

URL for content sharing for the Office 365 object

String: https://lawfirmwebsite.com

Optional

RemoveUrl

URL for removal.

String:

Optional

ChannelName

Specify the channel name

String - newchannel

Required for Channels

TabAppName

Specify the tab name

String - MyTab

Required for tabs

Office365Site

Specify the O365 site name. Sites and subsites now allow you to create from template. Include the template parameter.

String.

Required for Sharepoint

Office365SubSite

Specify the O365 sub site nameSites and subsites now allow you to create from template. Include the template parameter.

String

Optional for Sharepoint

SiteName

The name of the site that displays as the site title. This is required.

Required for Sharepoint

SiteCode

Specify the main sitecode to use for the Sharepoint (SiteCode is optional if you don’t specify the siteName) site.

String

Optional for Sharepoint

SiteCodeCollection

Allows the SiteCode Collection of user/group to be specified for use in Request Workflow for Grant Access to Sharepoint.

String

Required for Sharepoint

SubsiteName

The title of the subsite page. Is required.

Optional for Sharepoint

SubSiteCode

Specify a secondary or another sitecode for the Sharepoint site. Again similarly to the siteCode, this is optional if you don’t provide the subsiteName

String

Optional for Sharepoint

SiteType

Classic or Modern Sharepoint site type. Microsoft only has these two site types available.

String- Classic, Modern

Required for Sharepoint

SiteTemplate

Sets the template of the sharepoint site. Site templates depend on the site type you choose.

Modern site type available template parameters:

• COMMUNINCATION_SITE- The default modern sharepoint site template.
  NON_GROUP_TEAM_SITE

Classic site type available template parameters:

• TEAM_SITE

• BLANK_SITE- This is the default classic site template

• DOCUMENT_WORKSPACE

• BASIC_MEETING_WORKSPACE

• BLANK_MEETING_WORKSPACE

• DECISION_MEETING_WORKSPACE

• SOCIAL_MEETING_WORKSPACE

• MULTIPAGE_MEETING_WORKSPACE

• BLOG

• WIKI

• BASIC_GROUP_WORKSITE

• BLANK_GROUP_WORKSITE

String

Required for Sharepoint

Template

You can specify a template form template editor here, if you have a template of sites for sharepoint, a set of teams or channels or tabs for Teams.

String: Name of template

Optional

SiteDesignType

The design template in Microsoft to use. Example: showcase is the Showcase template. By default showcase is specified

• Topic to share information such as news, events, and other content.

• Showcase to use photos or images to showcase a product, team, or event.

• Blank to create your own design.

String

Required for Sharepoint

DisplayOrder

Sets the order of the tab, site or planner. If not set, then the order of the template will take precedence. See below JSON example.

Numerical: 1,2,3

Optional

PreviewType

Sets how the Planner task displays. See below JSON example. Also determines if show on card is checked or unchecked:

• NoPreview: Show on card will be unchecked.

• Automatic: Show on card will be unchecked.

• description: Show on card will be checked for the description for this task.

• Checklist: Show on card will be checked for checklist for this task.

• Reference: Not currently supported as attachments are unsupported.

String

Required for Planner

Description

The comment description for the channel/site.

String

Optional

Site_Id

It is the id of the sharepoint site.

Required

Graphid

it is the id for the driveid and includes the tenant first.

Optional

listURL

This is the URL and display name for the Sharepoint List. For example, https://examplefirm.sharepoint.com/sites/ListTemplates/Lists/DueDiligence/AllItems.aspx

String

Required for Sharepoint Lists

Security

This will set a user or groups security on the item. For example, the format is as follows: guru@camqa.onmicrosoft.com|true#null*Watcher$false". This means the guru user is active, and has role Watcher (Visitor) to the workspace.

String

Optional

Office365TeamIdCollection

This allows for better management of a user in a team. For example, if the metadata flag is set to true, then the logged-in user’s teams that he/she is a member of will display in the lookups in Request Workflow.

Please see Request Workflow for the steps to use this.

Bit

Yes/No, optional for Teams

Private Team and Channel Creation

A sample CSV to create a private team and channel

Private Team creation (only)

Creates a private team only

Planner Preview and order Sample

A JSON for setting the planner preview with order

Display Ordering Sample

Display Ordering of Projects, Sites, Meetings, Planner

Classic Site

Creates a Classic Site (showcase and team site)

Modern Site

Creates a Modern Site (Communication and showcase site)

Nested Sharepoint Sites

This creates multiple nested sharepoint sites (example does 3)

Site Creation with Security set

In this example, several workspaces are created, with three users having specific rights (admin, editor, watcher (visitor))