Skip to main content
AI ROI names people and shows their spend, so each viewer sees only what their role allows. The page, the nOps API and Clara’s tools all follow the same rules.

Roles

Before teams are set up in Manage teams, the approver of a Wallets group also sees that group on the Engineering Overview.

Give someone a role

Executive and engineering manager are permissions you add to a role.
  1. Go to Settings → Users and scroll to Organization Roles (see Roles and data scopes).
  2. Create a custom role, or edit one, and add ai-roi:executive or ai-roi:manager.
  3. Assign the role to the person.
Organization admins are executives without either permission.

Small groups

Totals for a group with fewer than 5 people who used AI in the range are shown only to people who may already see that group’s members (executives, and the team’s managers). This applies to organization totals and to a developer’s view of their own team. Without it, one person’s spend could be worked out from a team total. The same rule hides a small team’s scores from people outside it. A person’s own scores are visible to them and their managers only.

Restricted data scopes

AI ROI covers your whole organization. A user whose data scope limits them to part of it sees a message instead of a partial picture, because PRs and AI spend can’t be split by cloud account.

Developers who only use the agent

A developer who signs in to nOps for the first time to install the AI ROI Agent gets the restricted Developer role. It lets them approve their own machines and see their own AI ROI numbers, and nothing else in nOps. An admin can upgrade them to Member in Settings → Users at any time.