Technical Guide – netDocShare Provisioning Tool

Token

x-auth-key

x-auth-key is the header token and must be passed in the header of every API call. This is mandatory to execute any endpoints in Teams API.

Prerequisite:

Register an application in Azure portal and make a note of app id and app secret of the application. Then add the following Microsoft Graph API permissions to the registered application. The app id and app secret will be required to create the x-auth-key.

AppCatalog.Read.All	Application	Read all app catalogs
AppCatalog.ReadWrite.All	Application	Read and write to all app catalogs
Channel.Create	Application	Create channels
ChannelMember.Read.All	Application	Read the members of all channels
ChannelMember.ReadWrite.All	Application	Add and remove members from all channels
Contacts.Read	Application	Read contacts in all mailboxes
Contacts.ReadWrite	Application	Read and write contacts in all mailboxes
Directory.Read.All	Application	Read directory data
Directory.ReadWrite.All	Application	Read and write directory data
Files.Read.All	Application	Read files in all site collections
Files.ReadWrite.All	Application	Read and write files in all site collections
Group.Read.All	Application	Read all groups
Group.ReadWrite.All	Application	Read and write all groups
Organization.Read.All	Application	Read organization information
Organization.ReadWrite.All	Application	Read and write organization information
Profile	Delegated	View users’ basic profile
Team.Create	Application	Create teams
TeamMember.Read.All	Application	Read the members of all teams
TeamMember.ReadWrite.All	Application	Add and remove members from all teams
User.Read	Delegated	Sign in and read user profile
User.Read.All	Delegated	Read all users’ full profiles
User.Read.All	Application	Read all users’ full profiles
User.ReadWrite.All	Application	Read and write all users’ full profiles

Generate x-auth-key

x-auth-key should be created using the following information.


            var obj = { 


               appId: string, 

               appSec: string, 

               tenantId: string, 

               key: string, 

               key2: nounce 

               }

Keys in the Object:

appId -> string – App Client Id

appSec -> string – App Client Secret

key -> string – netDocShare License Key

tenantId -> string – Tenant Id

key2 -> current date and time as nounce.

Example to generate key2:

In JavaScript, this will be created using the code “Date.now()”.
In C#, this will be created using the code

“Convert.ToString((DateTime.Now.ToUniversalTime() - new DateTime(1970, 1, 1)).TotalMilliseconds + 0.5)”

Using the above Keys the Object obj will be generated.

Base 64 Conversion:

The Object obj will be converted to Base64 format. This Base64 string will be the x-auth-key.

In JavaScript, this conversion will be “btoa(JSON.stringify(obj))”
In C#, this conversion will be

var jsonData = JsonConvert.SerializeObject(obj).ToSrting)

System.Convert.ToBase64String(System.Text.ASCIIEncoding.ASCII.GetBytes(jsonData);

API URL

Base URL

The API base URL will be
var baseURL = https://provisioning.netdocshare.com/api/v1.0

Swagger

The full documentation of the API endpoints can be found in the below swagger link.

https://provisioning.netdocshare.com/api/v1.0/swagger/index.html

Teams API

Create a Team

URL end point	baseURL + “/msteams/teams”
Request Type	POST
Header	x-auth-key
Payload	{teamName, teamDescription, visibility, isSync, adminEmail, syncJobData}
Details of the payload can be found in the swagger documentation.

Sync Job Data sample:

{ “syncType”: “teamUni”,

“netDocuments”: {

“userName”: “Admin m365 KLoBot Demo”,

“cabinetId”: “NG-3MKEPV9J”,

“cabinetName”: “Clients”,

“repositoryId”: “CA-9ZYW8N4A”,

“workspaceId”: “”,

“workspaceName”: “”,

“workspaceEnvId”: “”,

“folderId”: “4884-4268-2150”,

“folderName”: “SK123_Sync”,

“breadCurmb”: [

{

“DocId”: “4868-8193-9491”,

“Attributes”: {

“Name”: “test”,

“Ext”: “ndfld”

“EnvId”: “:Q13:j:g:y:b:^F220603070712019.nev|1”

{

“DocId”: “4884-4268-2150”,

“EnvId”: “:Q14:b:g:h:v:^F220628130300487.nev”,

“Attributes”: {

“Name”: “SK123_Sync”,

“Ext”: “ndfld”

}

]

}

List all Teams

URL end point	baseURL + “/msteams/teams”
Request Type	GET
Header	x-auth-key

Fetch a Team

URL end point	baseURL + “/msteams/teams”
Request Type	GET
Header	x-auth-key
Path String	{id} – Team id

Update a Team

URL end point	baseURL + “/msteams/teams”
Request Type	PUT
Header	x-auth-key
Path String	{id} – Team id
Payload	{teamName, teamDescription, visibility, memberesNew, memberesRemove}
Details of the payload can be found in the swagger documentation.

Delete a Team

URL end point	baseURL + “/msteams/teams”
Request Type	DELETE
Header	x-auth-key
Path String	{id} – Team id

Create multiple Teams

URL end point	baseURL + “/msteams/teams”
Request Type	POST
Header	x-auth-key
Path String	{id} – Team id
Payload	{teamName, teamDescription, visibility, isSync, adminEmail, syncJobData}
Details of the payload can be found in the swagger documentation.

Channels

Create multiple Teams

URL end point	baseURL + “/msteams/teams/{id}/channels”
Request Type	POST
Header	x-auth-key
Path String	{id} – Team id
Payload	{channelName, channelDescription, membershipType, isSync, adminEmail, syncJobData}
Details of the payload can be found in the swagger documentation.

SyncJobData sample in 4.1

List all Channels

URL end point	baseURL + “/msteams/teams/{id}/channels”
Request Type	GET
Header	x-auth-key
Path String	{id} – Team id

Fetch a Channels

URL end point	baseURL + “/msteams/teams/{tid}/channels/{id}”
Request Type	GET
Header	x-auth-key
Path String	{tid} – Team id, {id} – Channel id

Update a Channels

URL end point	baseURL + “/msteams/teams/{tid}/channels/{id}”
Request Type	GET
Header	x-auth-key
Path String	{tid} – Team id, {id} – Channel id
Payload	{channelName, channelDescription}
Details of the payload can be found in the swagger documentation.

Delete a Channel

URL end point	baseURL + “/msteams/teams/{tid}/channels/{id}”
Request Type	DELETE
Header	x-auth-key
Path String	{tid} – Team id, {id} – Channel id
Payload	{channelName, channelDescription, membershipType, isSync, adminEmail, syncJobData}
Details of the payload can be found in the swagger documentation.

Create multiple Channels

Create a looping logic to create a channel with dynamic payload.

URL end point	baseURL + “/msteams/teams/{tid}/channels/{id}”
Request Type	POST
Header	x-auth-key
Path String	{id} – Team id
Payload	{channelName, channelDescription, membershipType, isSync, adminEmail, syncJobData}
Details of the payload can be found in the swagger documentation.

netDocShare Tab

Create a netDocShare Tab

URL end point	baseURL + “/msteams/teams/{tid}/channels/{cid}/tabs/netDocShare”
Request Type	POST
Header	x-auth-key
Path String	{tid} – Team id, {cid} – Channel id
Payload	{tabName, config}
Details of the payload can be found in the swagger documentation.

Config JSON string sample:

{ “viewType”:”RecentDoc”,

“primarySource”:

{

“id”:””,

“type”:””,

“name”:””

“sources”:[]

}

List all netDocShare Tabs

URL end point	baseURL + “/msteams/teams/{tid}/channels/{cid}/tabs”
Request Type	GET
Header	x-auth-key
Path String	{tid} – Team id, {cid} – Channel id

Fetch a netDocShare Tab

URL end point	baseURL + “/msteams/teams/{tid}/channels/{cid}/tabs/{id}”
Request Type	GET
Header	x-auth-key
Path String	{tid} – Team id, {cid} – Channel id, {id} – Tab id

Update a netDocShare Tab

URL end point	baseURL + “/msteams/teams/{tid}/channels/{cid}/tabs/{id}”
Request Type	PUT
Header	x-auth-key
Path String	{tid} – Team id, {cid} – Channel id, {id} – Tab id
Payload	{tabName}
Details of the payload can be found in the swagger documentation.

Delete a netDocShare Tab

URL end point	baseURL + “/msteams/teams/{tid}/channels/{cid}/tabs/{id}”
Request Type	DELETE
Header	x-auth-key
Path String	{tid} – Team id, {id} – Channel id

Create Multiple netDocShare Tabs

Create a looping logic to create a tab with dynamic payload.

URL end point	baseURL + “/msteams/teams/{tid}/channels/{cid}/tabs/netDocShare”
Request Type	POST
Header	x-auth-key
Path String	{tid} – Team id, {cid} – Channel id
Payload	{tabName, config}
Details of the payload can be found in the swagger documentation.

Bulk update of netDocShare Tab config

Create a looping logic to create a tab with dynamic payload.

URL end point	baseURL + “/msteams/teams/bulkConfigUpdate”
Request Type	POST
Header	x-auth-key
Path String	{data}
Details of the payload can be found in the swagger documentation.

data JSON string sample:

“data”: { “config”: {

“netcode”: false,

“viewType”: “Tree”,

“showLogo”: true,

“showLogout”: true,

“showSearchBox”: true,

“metaWebPartListLocation”: “”,

“metaWebPartTitle”: “”,

“contextMenu”: [

“post”,

“checkin”,

“checkout”,

“post”

“filters”: [],

“CDNBaseUrl”: “https://klobotappsdev.azurewebsites.net/apps/netdocshare/srvc/”,

“assetPath”: “https://klobotappsdev.azurewebsites.net/apps/netdocshare/assets/images/folderIcons”,

“AuthSuffix”: “auth”,

“docsPerPage”: “”,

“searchCriteria”: {

“field-date”: [

“ewdw”

]

“ndThread”: false,

“ndTasks”: true,

“authPage”: “”,

“menuSize”: “s”,

“TableDisplayDocsOnly”: false,

“clickBehavior”: “SLenabled”,

“searchBehavior”: “searchCurrentView”,

“workSpaceContentDisplay”: “ShowSummaryOrListView”,

“showParentInfo”: false,

“autoRefreshTimer”: 30,

“mandatoryEditProfile”: true,

“searchIn”: “title”,

“showWorkspaceName”: true,

“teamsPost”: true,

“teamsPostComments”: true,

“sources”: [

{

“id”: “4841-7567-1752”,

“name”: “1000 – Ironside Works”,

“type”: “workspace”,

“cabinet”: “Clients”,

“cabinetId”: “NG-3MKEPV9J”

}

“MSClientId”: “2cadc096-84c9-4183-b7a6-682ac908bdf0”

“teams”: [

{

“id”: “290d0a61-78ff-498f-b092-2c526bb0a198”,

“channels”: [

{

“id”: “19:[email protected]”,

“tabs”: [

{

“id”: “1cb89d15-317a-4451-a79b-2263822ad516”

}

]

}

]

{

“id”: “290d0a61-78ff-498f-b092-2c526bb0a198”,

“channels”: [

{

“id”: “19:[email protected]”,

“tabs”: [

{

“id”: “d3541ff5-f4b3-4fbe-912d-a37dd02c31b8”

{

“id”: “b4a65697-f499-416b-a667-44c8882906ce”

{

“id”: “21f0bd24-c8bf-4527-b05e-74a909571376”

{

“id”: “f1a2add5-d007-4062-a10a-60f4ea29fdbc”

}

]

}

]

}

]

}

Sync

Create Team Sync

URL end point	baseURL + “/msteams/teams/{tid}/syncjob/create”
Request Type	POST
Header	x-auth-key
Path String	{tid} – Team id
Payload	{ adminEmail, syncJobData}
Details of the payload can be found in the swagger documentation.

Sync Job Data sample:

{ “syncType”: “teamUni”,

“netDocuments”: {

“userName”: “Admin m365 KLoBot Demo”,

“cabinetId”: “NG-3MKEPV9J”,

“cabinetName”: “Clients”,

“repositoryId”: “CA-9ZYW8N4A”,

“workspaceId”: “”,

“workspaceName”: “”,

“workspaceEnvId”: “”,

“folderId”: “4884-4268-2150”,

“folderName”: “SK123_Sync”,

“breadCurmb”: [

{

“DocId”: “4868-8193-9491”,

“Attributes”: {

“Name”: “test”,

“Ext”: “ndfld”

“EnvId”: “:Q13:j:g:y:b:^F220603070712019.nev|1”

{

“DocId”: “4884-4268-2150”,

“EnvId”: “:Q14:b:g:h:v:^F220628130300487.nev”,

“Attributes”: {

“Name”: “SK123_Sync”,

“Ext”: “ndfld”

}

]

}

Create Channel Sync

URL end point	baseURL + “/msteams/teams/{tid}/syncjob/create”
Request Type	POST
Header	x-auth-key
Path String	{tid} – Team id
Payload	{ adminEmail, syncJobData}
Details of the payload can be found in the swagger documentation.

Delete Team Sync

URL end point	baseURL + “/msteams/teams/{tid}/syncjob/delete”
Request Type	DELETE
Header	x-auth-key
Path String	{tid} – Team id

Delete Channel Sync

URL end point	baseURL + “/msteams/teams/{tid}/channel/{cid}/syncjob/delete”
Request Type	POST
Header	x-auth-key
Path String	{tid} – Team id, {cid} – Channel id

Members

Search Members

URL end point	baseURL + “/msteams/teams/members”
Request Type	POST
Header	x-auth-key
Path String	{tid} – Team id
Payload	{ searchUserString}
Details of the payload can be found in the swagger documentation.

Add Members to a Team

URL end point	baseURL + “/msteams/teams/{tid}/syncjob/create”
Request Type	POST
Header	x-auth-key
Payload	{ teamId, members}
Details of the payload can be found in the swagger documentation.

List Channel Private Members

URL end point	baseURL + “/msteams/teams/{tid}/channels/{id}/privateMembers”
Request Type	GET
Header	x-auth-key
Path String	{tid} – Team id, {id} – Channel id

Template

Convert a Team to Template

URL end point	baseURL + “/msteams/teams/{id}/template”
Request Type	POST
Header	x-auth-key
Path String	{id} – Template id
Payload	{ templateName, templateDescription, visibility }
Details of the payload can be found in the swagger documentation.

Clone a Team from Template

URL end point	baseURL + “/msteams/teams/template/{id}/clone”
Request Type	POST
Header	x-auth-key
Path String	{id} – Template id
Payload	{ teamId, members}
Details of the payload can be found in the swagger documentation.

List all Templates

URL end point	baseURL + “/msteams/teams/template”
Request Type	GET
Header	x-auth-key

Update a Template

URL end point	baseURL + “/msteams/teams/template/{id}”
Request Type	GET
Header	x-auth-key
Path String	{id} – Template id
Payload	{ templateName, templateDescription, sync, syncType, config}
Details of the payload can be found in the swagger documentation.

Delete a Template

URL end point	baseURL + “/msteams/teams/template/{id}”
Request Type	DELETE
Header	x-auth-key
Path String	{id} – Template id

END-USER netDocShare LICENSE AGREEMENT

This is a Legally binding agreement between you (either an individual or a single entity) and KLoBot, Inc. (“KLoBot”) for the “netDocShare” Software and associated media and printed materials, and many include online or electronic documentation for netDocShare Software Product or netDocShare Software (collectively “netDocShare”). By installing, copying or otherwise using netDocShare, you are agreeing to be bound by the terms and conditions of this agreement, including netDocShare license and disclaimer of netDocShare software warranty below. Please read this document carefully before using netDocShare. If you do not agree with the terms and conditions of this agreement you should not install or use netDocShare.

1. GRANT OF LICENSE; netDocShare USE RESTRICTIONS.
In consideration for your payment of any applicable license fee for netDocShare, KLoBot hereby grants to you a personal, non-transferable (except as expressly provided in Section 4 below) and non-exclusive right to use and execute netDocShare on a single Microsoft Office 365 SharePoint Online Tenant or Microsoft SharePoint on-premises farm (collectively “tenant”), without right to sublicense netDocShare. Under no circumstance may you store, use or allow the use of netDocShare in any manner on more than one tenant at a time. You agree that you will not reverse engineer, decompile or disassemble any portion of netDocShare. If you dispose of any media or apparatus containing netDocShare, you will ensure that you have completely erased or otherwise destroyed any netDocShare contained on such media or stored in such apparatus. Except as expressly provided in Section 4 below, you may not distribute, lease, transfer for profit, loan or otherwise convey netDocShare or any portion thereof to anyone.

2. COPYING RESTRICTIONS.
In order to effect your license rights hereunder, you may install netDocShare by copying it onto the tenant for use thereon, and you may make full or partial copies of netDocShare, but only as necessary for backup or archival purposes. You agree that

(i) your use and possession of such copies shall be solely under the terms and conditions of this Agreement, and

(ii) you shall place the same proprietary and copyright notices and legends on all such copies as included by KLoBot on the authorized copy of netDocShare that you downloaded from the netDocShare web site.

3. OWNERSHIP OF netDocShare AND MEDIA.
You agree and acknowledge that KLoBot transfers no ownership interest in netDocShare, in the intellectual property in any netDocShare or in any netDocShare copy, to you under this Agreement or otherwise, and that KLoBot and its licensors reserve all rights not expressly granted to you hereunder. After you pay any applicable license fees and/or the purchase price of the applicable KLoBot, you will own the media on which netDocShare was originally provided to you hereunder and on which you subsequently copy netDocShare, but KLoBot and its licensors shall retain ownership of all netDocShare and copies of netDocShare or portions thereof embodied in or on such media.

4. TRANSFER RESTRICTIONS.
If you transfer ownership of netDocShare you may transfer netDocShare and all licenses and rights in netDocShare granted to you under this Agreement to the transferee provided that:

(i) such transferee agrees in writing to accept the terms and conditions of this Agreement, and

(ii) you also transfer all netDocShare, including all copies thereof, to such transferee. Except as provided in this Section, you may not sublicense, transfer or assign this Agreement or any of your rights or obligations under this agreement, in whole or in part.

5. U.S. GOVERNMENT USERS.
If netDocShare is acquired by or on behalf of an entity of government of the United States of America, the following provision applies: U.S. GOVERNMENT RESTRICTED RIGHTS LEGEND. Use, duplication or disclosure of SOFTWARE by the Government is subject to restrictions as set forth in FAR 52.227.19( c)(2) or subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer SOFTWARE clause at DFARS 252.227.7013 and/or in similar or successor clauses in the FAR or the DOD or NASA FAR Supplement. Unpublished rights reserved under the Copyright Laws of the United States. Contractor/manufacturer is KLoBot, Inc.

6. EXPORT RESTRICTIONS.
The software is exported from the United States in accordance with the Export Administration Regulations. Diversion contrary to U.S. law is prohibited. You agree that you will not:

(i) export or re-export the software, directly or indirectly, to Iran, Syria, Sudan, Cuba or North Korea; or

(ii) release the software to a person on the denied persons list, unverified list, entity list, specially designated nationals list, debarred list or nonproliferation sanctions list (see http://www.bis.doc.gov/complianceandenforcement/liststocheck.htm ). The foregoing obligations will apply to you unless the Office of Export Licensing of the U.S. Department of Commerce has granted authorization to you in writing for the export or re-export of the software. Your obligations under this section shall survive any termination of this Agreement.

7. ENFORCEMENT OF TERMS; TERMINATION.
If you fail to fulfill any of your material obligations under this Agreement, KLoBot and/or its licensors may pursue all available legal remedies to enforce this Agreement, and KLoBot may, at any time after your default of this Agreement, terminate this Agreement and all licenses and rights granted to you under this Agreement. You agree that KLoBot licensors referenced in netDocShare are third-party beneficiaries of this Agreement and may enforce this Agreement as it relates to their intellectual property. You further agree that, if KLoBot terminates this Agreement for your default, you will, within thirty (30) days after any such termination, deliver to KLoBot or render unusable all netDocShare originally provided to you hereunder and any copies thereof embodied in any medium.

8. DISCLAIMER OF SOFTWARE WARRANTY.
KLoBot PROVIDES netDocShare TO YOU AS IS AND WITHOUT WARRANTY OF ANY KIND, EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY ANY KLoBot EMPLOYEE, REPRESENTATIVE OR DISTRIBUTOR WILL CREATE A WARRANTY FOR THE netDocShare, AND YOU MAY NOT RELY ON ANY SUCH INFORMATION OR ADVICE.

9. INTELLECTUAL PROPERTY RIGHTS PROTECTION.
If any third party brings a suit against you that is based on a claim that netDocShare, solely as furnished to you under this Agreement, constitutes direct infringement of any patent issued by, or copyright registered in, the United states, KLoBot shall defend such suit or proceeding and shall pay any damages and costs finally awarded therein against you with respect to such matter, provided that you promptly inform KLoBot of any such claim, furnish KLoBot with a copy of each communication, notice or other action relating to the alleged infringement and give KLoBot the authority, information and assistance necessary to settle, compromise or litigate such suit or proceeding. Following notice of a claim or a threatened or actual suit, KLoBot may, without obligation to do so, at KLoBot sole option:

(a) procure for you the right to continue to use netDocShare as furnished,

(b) replace or modify netDocShare to make it non-infringing, or

(c) discontinue your license for netDocShare and refund to you any license fee that you paid for it, less a reasonable value for use, determined by prorating such license fee on the basis of a thirty-six (36) month straight line depreciation method, applied to the period of actual use.

KLoBot shall not be obligated to defend or be liable for costs and damages if the infringement or claim thereof arises out of:

(i) use or combination of netDocShare with products or data not provided by KLoBot,

(ii) use of other than the latest unmodified release of netDocShare made available to you by KLoBot if such infringement would have been avoided by the use of such release of netDocShare,

(iii) modification of netDocShare by anyone by KLoBot,

(iv) use of netDocShare after receiving notice, or having reason to believe, that netDocShare infringes a patent or copyright of a third party, or

(v) a claim based on any portion of the Windows(r) software that may be included with netDocShare.

THE FOREGOING STATES YOUR EXCLUSIVE REMEDY AND KLoBot ENTIRE LIABILITY WITH RESPECT TO INFRINGEMENT OF ANY PATENT OR COPYRIGHT BY netDocShare, AND KLoBot SHALL HAVE NO LIABILITY WITH RESPECT TO ANY OTHER INTELLECTUAL PROPERTY RIGHT.

10. GOVERNING LAW.
This Agreement shall be governed by and interpreted in accordance with New Jersey law, excluding its choice of law rules.

11. TECHNICAL SUPPORT TERMS.

Definitions.As used herein the following capitalized terms have the meanings set forth below:

“Correction” means, without limitation, a workaround, maintenance release, patch and/or documentation change, as KLoBot deems appropriate.
“Defect” means a material failure of netDocShare to operate substantially in accordance with the applicable user guides and reference manuals.
“Update” means a maintenance or minor release of netDocShare that provides corrections or performance improvements, is designated by KLoBot as an Update and is generally made available to all KLoBot technical support customers.
“Upgrade” means a major release of netDocShare that provides new features or functional enhancement, is designated by KLoBot as an Upgrade and is generally made available to KLoBot Premium technical support customers.

Technical Support.

During any 12/24/36-month support period for which you have pre-paid the required premium support payment, KLoBot will provide you:

Notification, if you have requested to be notified, when Updates are available for downloading from netDocShare website at www.netdocshare.com ;
Notification, if you have requested to be notified, when Upgrades are available for downloading from KLoBot’ website; and
Access to My netDocShare Support Portal on KLoBot’ website through which you may:

- Download Updates when commercially available;
- Download Upgrades (Premium technical support customers only) when commercially available;
- Report Defects in netDocShare and obtain Corrections as described herein and in accordance with the types of response and timing referenced on KLoBot’ website;
- Request General advice on implementation, operation, functionality and use of netDocShare as described on KLoBot’ website;
- Participate in community forums, review KLoBot’ extensive knowledge base and obtain usage tips and other useful information regarding netDocShare, including up-to-date information on current releases, product compatibility, restrictions, enhancements, workarounds and fixes; and
- Access on-line documentation regarding netDocShare, including application notes that include installation instructions, release notes and Frequently Asked Questions (FAQs).

Defect Correction.

When you report a suspected Defect in netDocShare to KLoBot using its My netDocShare Support Portal, KLoBot will attempt, based upon information provided by you, to recreate the suspected Defect. If the Defect is confirmed, KLoBot will use commercially reasonable efforts, given the nature and scope of the Defect, to make available to you through the My netDocShare Support Portal a Correction in accordance with the guidelines set forth on KLoBot’ website. KLoBot will make available to Premium technical support customers live chat, telephone call back and live meeting support as appropriate and warranted to confirm Defects and develop Corrections.
KLoBot will not be responsible for correcting Defects in any release of netDocShare other than the most recent release of netDocShare, provided that KLoBot shall continue to support the prior release superseded by recent release for a reasonable period sufficient to allow Premium technical support customers to implement the newest release or until the end of the current non-Premium technical support period.
You agree to implement within a reasonable time all Corrections provided by KLoBot hereunder.

Limitations.

KLoBot will not be obligated to provide technical support relating to problems, errors or malfunctions caused by

malfunction of the computer system and communications network on which you have installed and are using netDocShare,
other software installed in the same SharePoint environment not licensed pursuant to this Agreement,
any use of netDocShare in disregard of any known adverse consequences, including without limitation the failure of user to make appropriate backups, warning messages, and other written instructions,
any modification to netDocShare not authorized by KLoBot,
Mainstream Support of a given SharePoint Platform has been retired by Microsoft, or
any other cause not attributable to KLoBot.

Renewal of Support.

KLoBot provides the first year of basic technical support for no additional charge. Unless renewed in accordance herewith, basic technical support will cease on the last day of the 12-month support period that commenced upon the effective date of netDocShare license.
For an additional fee, you may obtain Premium technical support. Unless renewed in accordance herewith, Premium technical support will cease on the last day of the support period for which you have paid the additional Premium technical support fee.
Support fees for additional support periods must be paid in advance on or prior to last day of the support period for which you have paid the required support fee.
Approximately forty-five (45) days prior to the termination of the then current support period, KLoBot will invoice you for renewal of technical support. The support fee due for the next support period shall be KLoBot’ then current applicable list price for renewal of technical support as of the date of invoice.
KLoBot reserves the right to withdraw technical support of netDocShare, and to alter the prices, terms and conditions for technical support in advance of any renewal of support. Any such withdrawal or alterations will become effective as of such renewal date.

Reinstatement of Support.

If you allow technical support to expire, in order to reinstate support of netDocShare, you may be required to pay to KLoBot a reinstatement support fee, the then current annual support fee, and, If you are not licensing the then current release of netDocShare, an upgrade license fee for the current release of netDocShare.
Required Identifier.

In order to access My netDocShare Support Portal you must provide the identifier issued to you when you licensed netDocShare. Upon entry of such identifier access will be granted if you have paid in full the required maintenance fee.
Termination of Technical Support.

Notwithstanding Section 4 above, resale, assignment, or transfer of the technical support provided by KLoBot is strictly prohibited and will be grounds for termination of the technical support.

Connect with us

Technical Guide – netDocShare Provisioning Tool

netDocShare

Connect with us