You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+13-3Lines changed: 13 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,7 @@ Toolkit is a deployable all-in-one RAG application that enables users to quickly
16
16
-[How to setup Gmail](/docs/custom_tool_guides/gmail.md)
17
17
-[How to setup Slack Tool](/docs/custom_tool_guides/slack.md)
18
18
-[How to setup Github Tool](/docs/custom_tool_guides/github.md)
19
+
-[How to setup Sharepoint](/docs/custom_tool_guides/sharepoint.md)
19
20
-[How to setup Google Text-to-Speech](/docs/text_to_speech.md)
20
21
-[How to add authentication](/docs/auth_guide.md)
21
22
-[How to deploy toolkit services](/docs/service_deployments.md)
@@ -28,30 +29,39 @@ Toolkit is a deployable all-in-one RAG application that enables users to quickly
28
29

29
30
30
31
## Try Now:
31
-
There are two main ways for quickly running Toolkit: local and cloud. See the specific instructions given below.
32
+
33
+
There are two main ways for quickly running Toolkit: local and cloud. See the specific instructions given below.
34
+
32
35
### Local
33
-
*You will need to have [Docker](https://www.docker.com/products/docker-desktop/), [Docker-compose >= 2.22](https://docs.docker.com/compose/install/), and [Poetry](https://python-poetry.org/docs/#installation) installed. [Go here for a more detailed setup.](/docs/setup.md)*
36
+
37
+
_You will need to have [Docker](https://www.docker.com/products/docker-desktop/), [Docker-compose >= 2.22](https://docs.docker.com/compose/install/), and [Poetry](https://python-poetry.org/docs/#installation) installed. [Go here for a more detailed setup.](/docs/setup.md)_
34
38
Note: to include community tools when building locally, set the `INSTALL_COMMUNITY_DEPS` build arg in the `docker-compose.yml` to `true`.
35
39
36
40
Both options will serve the frontend at http://localhost:4000.
37
41
38
42
#### Using `make`
43
+
39
44
Use the provided Makefile to simplify and automate your development workflow with Cohere Toolkit, including Docker Compose management, testing, linting, and environment setup.
Use Docker Compose directly if you want to quickly spin up and manage your container environment without the additional automation provided by the Makefile.
docker compose run --build backend alembic -c src/backend/alembic.ini upgrade head
53
61
```
62
+
54
63
### Cloud
64
+
55
65
#### GitHub Codespaces
56
66
57
67
To run this project using GitHub Codespaces, please refer to our [Codespaces Setup Guide](/docs/github_codespaces.md).
@@ -63,7 +73,7 @@ To run this project using GitHub Codespaces, please refer to our [Codespaces Set
63
73
-**Interfaces** - any client-side UI, currently contains two web apps, one agentic and one basic, and a Slack bot implementation.
64
74
- Defaults to Cohere's Web UI at `src/interfaces/assistants_web` - A web app built in Next.js. Includes a simple SQL database out of the box to store conversation history in the app.
65
75
- You can change the Web UI using the docker compose file.
66
-
-**Backend API** - in `src/backend` this follows a similar structure to the [Cohere Chat API](https://docs.cohere.com/reference/chat) but also include customizable elements:
76
+
-**Backend API** - in `src/backend` this follows a similar structure to the [Cohere Chat API](https://docs.cohere.com/reference/chat) but also include customizable elements:
67
77
-**Model** - you can customize with which provider you access Cohere's Command models. By default included in the toolkit is Cohere's Platform, Sagemaker, Azure, Bedrock, HuggingFace, local models. [More details here.](/docs/command_model_providers.md)
68
78
-**Retrieval**- you can customize tools and data sources that the application is run with.
69
79
-**Service Deployment Guides** - we also include guides for how to deploy the toolkit services in production including with AWS, GCP and Azure. [More details here.](/docs/service_deployments.md)
To setup the Sharepoint tool you need to configure API access via the following steps
4
+
5
+
## 1. Configure Tenant ID and Client ID
6
+
7
+
Your Microsoft Tenant ID and Client ID can be found my navigating to the [Micorsoft Entra Admin Center](https://entra.microsoft.com/) and then going to the `Overview` Page under the `Identity Section`. There the Tenant ID is listed as Tenant ID, and the Client ID is listed as the Application ID.
8
+
9
+
Copy your Tenant ID into the `configuration.yaml` file in the config directory of the backend, and your Client ID into the `secrets.yaml` file in the config directory of the backend.
10
+
11
+
## 2. Register New Application
12
+
13
+
Navigate to the `App registration` page under `Applications` on the same [Micorsoft Entra Admin Center](https://entra.microsoft.com/) website.
14
+
15
+
Click `New registration` to register a new application. Enter a name and select the proper account type. Single tenant is the norm unless you know of otherwise.
16
+
17
+
Under redirect URI select Web as the path should be `/v1/tool/auth`. For example:
18
+
19
+
```bash
20
+
https://<your_backend_url>/v1/tool/auth
21
+
```
22
+
23
+
Click `Register` to Complete the Application Registration
24
+
25
+
## 3. Configure Permissions
26
+
27
+
Under the newly registered application navigate to the `API permissions` page. There you need to Click `Add a permission`, select `Microsoft Graph`, then `delegated permissions`. Next search `files.read.all` and check the box, then search `sites.read.all` and check the box. Then Click `Add permissions`.
28
+
29
+
## 3. Configure Client Secret
30
+
31
+
Under the newly registered application navigate to the `Certificates & secrets` page. Click `New client secret`, enter a description and an expiry then click `Add`. Your new Client Secret is only available to copy under the `value` column of the table right now. Copy it into the `secrets.yaml` file in the config directory of the backend.
32
+
33
+
## 5. Run the Backend and Frontend
34
+
35
+
run next command to start the backend and frontend:
assertresult== [ToolError(type=ToolErrorCode.OTHER, success=False, text='No results found.', details='No results found for the given params.').model_dump()]
assertresult== [ToolError(type=ToolErrorCode.OTHER, success=False, text='No results found.', details='No results found for the given params.').model_dump()]
0 commit comments