Skip to content

Commit 079ba07

Browse files
authored
Latest updates for Workspace and Multi-turn feature (#530)
* Docs * Add docs for multi turn and workspaces * Add Tony as author
1 parent a33257a commit 079ba07

File tree

3 files changed

+68
-0
lines changed

3 files changed

+68
-0
lines changed
96.5 KB
Loading

docs/blog/posts/multi-turn.md

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
---
2+
authors:
3+
- Tony
4+
category:
5+
- Admin App
6+
- Chat
7+
date: 2025-04-15
8+
---
9+
10+
# Introducing Multi-turn Chat
11+
12+
Ever wanted to ask follow-up questions without losing context from previous answers?
13+
We’ve now got you covered with our brand-new **multi-turn chat** endpoint. Just keep asking, and the chat remembers what you said before.
14+
15+
<!-- more -->
16+
17+
## Why did we build this?
18+
19+
Managing user question on-the-fly often means juggling multiple questions and follow-ups. This can get tricky when new messages layer onto an ongoing conversation. Multi-turn chat solves that by keeping track of your entire conversation history, so your questions can seamlessly connect to prior answers.
20+
21+
To learn more visit the [Multi-turn Chat Setup page](../../components/multi-turn-chat/index.md)
22+
23+
## Doc references
24+
25+
- [Multi-turn Chat](../../components/multi-turn-chat/index.md)

docs/blog/posts/workspaces.md

Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
---
2+
authors:
3+
- Tony
4+
category:
5+
- Admin App
6+
- Workspaces
7+
date: 2025-04-15
8+
---
9+
10+
# Introducing Workspaces
11+
12+
Need a better way to organize your projects, data, and user roles?
13+
Meet **Workspaces**—isolated virtual environments designed to simplify access management across multiple projects or teams. With the Workspaces feature, you get a cleaner, more secure, and more flexible approach to data sharing.
14+
15+
<!-- more -->
16+
17+
![Workspace screenshot](../../components/workspaces/swagger-user-and-workspace-screenshot.png){: .blog-img }
18+
19+
## Why Workspaces?
20+
21+
Previously, every user was a de facto admin with unlimited read/write privileges in their environment. To share data with someone else, you had to reveal your personal credentials, granting them the same authority you had. This setup made it hard to manage sensitive data and user permissions effectively.
22+
23+
## The Workspace Approach
24+
25+
Workspaces completely overhaul this system:
26+
27+
1. **Isolated Virtual Environments**
28+
Each workspace contains its own set of content, quotas, and users, meaning no accidental overlaps or data spills.
29+
30+
2. **Many-to-Many Relationship**
31+
Users can belong to multiple workspaces, and each workspace can have multiple users. Permissions are specific to each workspace.
32+
33+
3. **Role-based Access**
34+
There are two main user types out of the box:
35+
36+
- **Admin**: Full access to create, read, update, and delete data in their assigned workspace(s). They can add or remove users (including other admins), plus create new workspaces or remove their own.
37+
- **Read-Only**: Can only read existing data in their assigned workspace(s). They can create new workspaces but cannot modify data or user assignments within their current workspace(s).
38+
39+
To learn more about this new feature visit the [Workspaces Overview page](../../components/workspaces/index.md)
40+
41+
## Doc References
42+
43+
- [Workspaces Overview](../../components/workspaces/index.md)

0 commit comments

Comments
 (0)