Ian On Docs
Features

Collaboration

The page where you see your teams' work, events, and shared knowledge together, the manager's Team Flow, and what you can see depending on your role and team membership.

Collaboration is where you see your teams' work, events, and shared knowledge together with your teammates. Open it from Collaboration in the left menu. Anyone who belongs to a team uses it, whatever their role. Even owners and admins see only the teams they directly belong to.

Each of your teams shows its name, its member count, and up to 6 of its work cards. Press Open collaboration to open that team's page. If you don't belong to any team, the message You don't have Collaboration access yet. appears, so ask an admin to add you to a team.

Owners and admins create accounts and manage the organization's members in Admin → Organization & members.

The team page

Press Team Ian chat under the team name to open the Ian conversation linked to this team. A Manager also sees Open Manager Team Flow (see Team Flow below). Below that are the member count and three areas.

  • Outcome Briefs — this team's work cards that you can see through your current team membership.
  • Upcoming team events — upcoming events scheduled for this team. Each event shows how it relates to you, such as Organized by me or Required invite.
  • Recently shared knowledge — the 5 most recent documents shared with this team that have finished analysis. Press a document or All knowledge to open this team's Knowledge screen.

A work card shows its status, the Expected result, a summary of the latest Result with the time it was recorded, and the Current driver, plus the Latest artifact if there is one. Blocked work is marked Blocked. Press a card to open that work. Below the card, you see why this work is visible to you (for example, You are the current driver or Current team membership).

In Start an Outcome, enter a Problem and an Expected result to create team work that people carry out themselves.

In Team Ian chat, you can share what Ian remembered to team knowledge by saying "Share this with the team". Only the items Ian recently remembered in this conversation are shared, and your personal memory stays as it is. Items that can't be shared, such as content that needs team review, aren't shared, and Ian tells you why.

If work, events, or shared knowledge fail to load, an error appears in that area. Press Try again to load it again.

Team Flow

If you have the Manager role, Open Manager Team Flow appears on your teams' pages. Owners, admins, and members don't see it. Team Flow is a page for supporting the team, not for evaluating individual performance.

  • Needs support — blocked work, work with no driver, open handoffs and reviews (including overdue ones), open help requests, and team decisions waiting on a manager.
  • Current accepted commitments — work commitments in progress, accepted handoffs, and help commitments.

For a team decision nobody has taken yet, take it first with Claim. For a decision assigned to you or one you claimed, press Approve or Reject. On other cards, buttons such as Open Work take you to the related work.

The four roles

  • Owner — can do everything an Admin can, and can also make someone else an owner or change another owner's role or account status.
  • Admin — runs the organization from the Admin menu: members and teams, AI providers, connections, agents, and more. Can't make someone an owner or change an owner's role.
  • Manager — sees Team Flow for their teams, handles team decisions, and manages their teams' documents. Doesn't see the Admin menu.
  • Member — the standard role: uses their own personal work and the team work and shared knowledge they can access.

Owners and admins change a role by editing the member in Admin → Organization & members, and every change is written to the audit log. You can't change your own role, and the last active owner's role can't be changed either.

What you can see

Team membership, more than role, decides what you can see. Once you belong to a team, you see that team's work and documents without any separate grant.

  • Work — only the creator sees personal work, and only a team's members see that team's work. Even owners and admins can't see someone else's personal work or the work of a team they don't belong to.
  • Knowledge — every member sees Global documents, and a team's members see that team's documents. Only owners and admins can upload as Global.
  • Database connections & tools — owners and admins register database connections and also decide which agents or teams use them (Database connections). Whether an agent can use tools such as web browsing or code execution is set per agent in Tool permissions in Agents.

When a new member says "my screen is empty," check their team membership first. If they don't belong to any team, Collaboration shows You don't have Collaboration access yet. and they can't see any team work or documents either. Owners and admins add team membership in Admin → Organization & members.

When someone leaves

When an owner or admin turns off Account active for a member in Admin → Organization & members, that person immediately can't sign in or use the app. Their personal work in progress is Paused, and team work they were driving is also Paused and its driver is cleared. The account and its history and audit records stay intact. To let them back in, turn Account active on again for the same account. You can't invite someone or add a new account with the email of a deactivated account.

On this page