{"id":7462,"date":"2026-08-19T19:10:05","date_gmt":"2026-08-19T19:10:05","guid":{"rendered":"https:\/\/www.wiven.ai\/wiven-llm\/docs\/utilisation\/espaces-de-travail\/"},"modified":"2026-08-19T19:10:05","modified_gmt":"2026-08-19T19:10:05","slug":"espaces-de-travail","status":"publish","type":"wvn_doc","link":"https:\/\/www.wiven.ai\/en\/wiven-llm\/docs\/utilisation\/espaces-de-travail\/","title":{"rendered":"Workspaces"},"content":{"rendered":"

Workspaces<\/h1>\n

The workspace is the central unit of WivenLLM. It includes of the
\ndocuments<\/strong>, settings<\/strong> And conversations<\/strong>, and determines what
\nThe assistant can see.<\/p>\n

\n

What a workspace contains<\/h2>\n\n\n\n\n\n\n\n\n\n\n\n
Element<\/th>\nScope<\/th>\n<\/tr>\n<\/thead>\n
Indexed documents<\/td>\nOnly this space<\/td>\n<\/tr>\n
Prompt system<\/td>\nOnly this space<\/td>\n<\/tr>\n
Conversation model and agent model<\/td>\nOnly this space<\/td>\n<\/tr>\n
Search parameters<\/td>\nOnly this space<\/td>\n<\/tr>\n
Agent skills activated<\/td>\nOnly this space<\/td>\n<\/tr>\n
Conversations and threads<\/td>\nOnly this space<\/td>\n<\/tr>\n
Members<\/td>\nOnly this space (in multi-user mode)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The two spaces share nothing.<\/strong> A question asked in one cannot
\naccessing the other party's documents. This guarantees compartmentalization of the
\nproduct \u2014 one that allows, for example, one space per customer without risk of
\nleak between files.<\/p>\n

One exception, voluntary and personal: the
\nSecond Brain<\/a>, which traverses spaces but does not belong
\nthan to you.<\/p>\n

\n

How to cut them<\/h2>\n

The correct cutting is by confidentiality perimeter and by corpus<\/strong>, not by
\ntopic of conversation.<\/p>\n

Create a separate space when:<\/strong>
\n\u2013 the documents must not be mixed up (one client, one file, one entity); ;
\n\u2013 the instructions differ (a legal space and a commercial space do not have
\n the same prompt system); ;
\n\u2013 the authorized persons are not the same; ;
\n\u2013 the model must be different (one sensitive space in a purely local context, another on
\n an external supplier).<\/p>\n

Stay in the same space when<\/strong> This is simply another topic of
\nconversation: then use a thread<\/strong>.<\/p>\n

Two typical breakdowns<\/h3>\n

Per customer<\/strong> \u2014 one space per client, each containing only their own items. The
\nPartitioning is structural. Suitable for trustees, firms, agencies.<\/p>\n

By domain<\/strong> \u2014 a \u00abtechnical documentation\u00bb area, an \u00abHR\u00bb area, a
\n"Quality" space. Suitable for organizations with a shared corpus but
\nthematic.<\/p>\n

\n

Discussion threads<\/h2>\n

In a space, each thread<\/strong> is an independent conversation with its own
\nhistory. All threads in a space share the same documents and the same
\nsettings.<\/p>\n