Build Agents.Share Them Securely With the Right People.
Builders create agents, admins decide who can use them and under what rules, and users across teams and trusted partners run them on their own work. Each team stays on the version it depends on, access ends when it should, and every grant, use and revocation is on the record.
- v13TodayTests passed
- v12May 3Tests passed
- v11March 12Tests passed
A sample shared agent. All teams, partners and numbers are made up.
How Sharing Works
The same four steps for a team down the hall or a partner across the world.
Admins, Builders and Users
People who use an agent should not be able to change it, and people who build it should not be the only ones who approve it. Three roles keep those lines clear, synced from your identity provider.
Admins
- Set policies, roles and approval rules
- Approve publishing and external sharing
- See usage, cost and the audit trail across teams
Builders
- Create and change agents, prompts, tools and knowledge
- Test new versions against graded cases
- Publish only after an admin approves
Users
- Run the agents shared with their team
- Stay on the version their team pinned
- Cannot change prompts, tools or knowledge
Roles follow your identity provider and your separation-of-duties rules. Owners and approvers are always recorded.
Teams Upgrade When They Are Ready
Each team stays on the version it depends on, so an improvement for one team never changes another team’s results overnight. A new version is offered only after it passes the same tests on the same cases.
Pinned by Default
Teams keep their version until they choose to move, and see when a newer one is available.
Tested Before It Is Offered
A new version must beat or match the last one on graded cases before anyone can upgrade.
Roll Back in One Step
If a version causes a problem, teams return to the last good one immediately.
Do all VEL-301 site agreements include the updated indemnity language from March?
Context config
46 of 48 VEL-301 site agreements include the March indemnity language.Agent · 48 agreements
Sites 114 and 207 still use the earlier version and need an amendment.Site agreements 114, 207
Share With Partners Without Sharing Everything
Give a research partner, supplier or outside counsel access to one agent and only the data that belongs to your work together. Everything else stays inside your organization, and access ends on the date you set.
One Agent, One Scope
Partners use a specific agent version with only the knowledge and data you include.
Approved Before It Starts
External access follows your approval rules, and nothing is shared until it is approved.
Ends When the Work Ends
Every external grant has an end date and can be withdrawn at any time.
Who Used What, and Why They Could
Every grant, use, upgrade and revocation is recorded with who did it and when, so an access review takes minutes instead of weeks.
Recorded for every shared agent
- Who granted access, to whom, with which role and why
- Which version each team used, and how often
- Approvals for external sharing, with the approver named
- Upgrades and rollbacks, with the test results behind them
- Revocations, with the reason and the time
- Access reviews exported for your auditors
Related Modules
The platform modules these solutions are built on.
Frequently Asked Questions
Common questions about ThinkTrends Teams & Agent Sharing.
What is Teams & Agent Sharing in ThinkTrends?
+
Teams & Agent Sharing lets organizations share a proven AI agent with other teams and trusted partners instead of rebuilding it. Builders create agents, admins grant access and approve sharing, and users run the agents shared with them, each team pins the version it depends on, external access is scoped and time-limited, and every grant, use and revocation is recorded.
How is ThinkTrends agent sharing different from sharing a custom GPT or Copilot agent?
+
Sharing a custom GPT or Copilot agent usually gives people the agent as it is today. ThinkTrends separates admin, builder and user rights, pins each team to a tested version, requires approval and an end date for partners, limits partners to the data you choose and keeps a complete access log.
Can we share an AI agent with an external partner?
+
Yes. ThinkTrends shares a specific agent version with a partner such as a research organization, supplier or outside counsel, limited to the knowledge and data you include. External access follows your approval rules and ends on the date you set.
What happens to teams when a shared agent is updated?
+
Nothing changes for them until they choose. Each team stays on its pinned version and sees when a newer version is available. A new version is offered only after it passes the same tests on the same graded cases, and teams can roll back in one step.
How do we revoke access to a shared agent?
+
The owner withdraws access in one step for a team, a person or a partner. Revocation takes effect immediately and is recorded with the reason and the time.
What are admins, builders and users in ThinkTrends?
+
They are the three roles for shared agents. Admins set policies, approve publishing and external sharing, and see usage and the audit trail. Builders create, change and test agents. Users run the agents shared with their team on the version their team pinned. Roles sync from your identity provider.
Is our data used to train AI models?
+
No. ThinkTrends uses agents, documents and logs only to do the work, inside your own environment. Your data is never used to train, tune or evaluate a model.