Share files, folders, sessions, and workflow outputs
Sharing in Nomic depends on the thing you are sharing — and on your plan.
Individual plan: sessions can be Private or Anyone with the link. Recipients sign in (or sign up) to open the link. You cannot invite project members or share workflows with an organization.
Business and Enterprise: file visibility, project access, workflow visibility, and session sharing are related, but they are not the same.
Files and folders
Files can be private, shared through a project, or visible through an integration. If a file comes from SharePoint, Egnyte, Autodesk Forma, or another connected system, Nomic respects the source permissions.
If a teammate cannot see a file:
- Confirm they can open it in the source system.
- Confirm the file is part of the project or folder they are using.
- Confirm the file has synced and indexed.
- Confirm they are using the right Nomic tenant.
If someone opens a shared file, project, workflow, or cited file that they cannot access, Nomic shows a dedicated access screen with guidance to ask the owner to share it. This means the link may be valid even when the viewer needs additional access.
Projects
Project access controls who can see project context. Adding someone to your Nomic organization does not automatically give them access to every project or file.
Use projects when multiple people need a shared workspace for files, workflow runs, and review context.
Assistant sessions
Assistant sessions are private by default. Only the session owner can see the conversation until they explicitly share it.
How to share a session
- Open the session you want to share.
- Click Share in the chat header.
- Choose a visibility level:
- Private — only you can see this chat.
- Anyone with the link (Individual) — anyone signed in with the link can see this chat and its uploaded files.
- Shared in Project (Business and Enterprise) — project members can see this chat. This option is available when the session belongs to a project.
- Shared in Org (Business and Enterprise) — anyone in your organization with the link can see this chat.
- If the chat includes private uploaded files, review the warning and click Manage to decide which files to share.
- Copy the share link and send it to your teammate.
You can also change visibility from the session menu in the sidebar.
Changing visibility controls who is allowed to open the session. It does not guarantee the session will appear automatically in every teammate's sidebar. If someone needs to review a specific past session, send them the share link or make sure the session belongs to a project they already use.
What shared viewers can do
Teammates who receive a shared session can view the full conversation, including citations and reasoning. They cannot continue the conversation or send new messages — only the session owner can do that.
Important: check the underlying files
Sharing a session gives your teammate access to the conversation. File access is handled separately, so always check whether the session uses files your teammate can open.
When a shared chat includes private uploaded files that you own, Nomic shows a warning in the share dialog. Click Manage to open Share files, then:
- Individual — share uploaded files with the link recipients.
- Business and Enterprise — share uploaded files with your organization (Share or Share all with organization).
- Review External integration files. These keep their source-system permissions and cannot be shared from the chat dialog.
If the session cites or references files your teammate still does not have access to, they will be able to see the conversation and citations but may not be able to open or view those files.
To make sure your teammate can see everything:
- Confirm they have access to the relevant files in the source system (SharePoint, Egnyte, ACC, etc.).
- Confirm the files are part of a project your teammate belongs to, or share uploaded files from the chat dialog or file menu.
Before sharing, check whether the session includes private files or sensitive context.
Workflows and workflow outputs
Individual plan: skip this section. Workflows stay in your account.
Workflow sharing is separate from file and session sharing. On Business and Enterprise, the workflow's Sharing tab lets you:
- Keep it Invited people only and invite specific people as Can run or Can edit.
- Promote it to Everyone in your organization (or everyone in the project, for a project-scoped workflow).
Teammates who can run a workflow still only see the files and project context they personally have access to. Saved edits stay in draft until you release a version; runners use the live version. See Workflow management for roles, promotion, and versioning.
Workflow outputs, including artifacts, follow the permissions of the run or session that produced them. Sharing a run or session lets teammates view the generated outputs, while source file access is still checked separately.
Workflow outputs can usually be shared by:
- Sharing the workflow run
- Exporting a table or report
- Downloading a marked-up drawing
- Moving the output into your team's normal review process