By default, somebody on your roster sees their own score and nobody else's.
Owners and admins see the team view, on a plan that carries it. That does not change with any setting.
There is one setting that decides whether ordinary members can see each other's scores. It is off unless an owner has turned it on.
A score sitting next to a person's name is the sort of thing that gets talked about at the till and in the staff room. Turning that on across a whole team is a decision about the place people work, not a display preference, so it starts off and somebody has to choose it.
Not an admin. This edits what colleagues may learn about each other, which sits with the person accountable for the organization, in the same bracket as closing it.
Any member can read the setting, including members who cannot change it. The person most affected by "can my colleagues see my score" is the person whose score it is, so they are allowed to find out the answer without asking anybody.
There is no page in the web app today where an owner can turn this on or off. The setting is real and it is enforced on the server, but the only way to change it right now is through the API.
In practice that means it is off for your organization unless somebody has deliberately changed it.
When it is off, a member still reaches these views on a plan that carries them, but sees only their own row:
the team score board, which needs the Team plan
the per-member Work Scores, which need the Business plan
the organization's commitment ledger, which needs the Team plan
The AI narration of the organization is refused outright for members when the setting is off, rather than narrowed. A summary of one person is not an honest version of a summary of a team, so it is not offered.
Engineering health is not covered by the setting at all. It is a view of the system and it names nobody.
Turning the setting on or off changes nobody's score. In Credda's own words:
“Nobody's score changed: this decides who may read a number, never the number.”
A member always keeps their own Work Score, identical in both positions. Nobody loses sight of their own record.
Supervisors are refused this whole set of views in both positions. The supervisor rule runs first, so the setting can only narrow a door that is already open, never open one.
Every change is written into your organization's activity feed as a change to score visibility, recorded with a role and the new policy, never with a name.
If your organization uses the developer activity view, it is available to owners and admins only, in both positions of the colleague setting.
Be careful with it. It reports what is in somebody's connected code account, which is their whole account: personal projects, weekend work, and work they did for other employers. It is not scoped to the work they did for you. Ask yourself whether you want to know that before you look at it.
Who confirmed somebody's work. Credda never shows a confirmer's identity on a shared record. A reader sees the role of the person who confirmed and how many separate parties confirmed things, and no name, address, initial or company domain.
Who has looked at a record. A person can see how many times their own record was viewed. There is no viewer list, for them or for you, and Credda cannot produce one either. Views are stored in a form that cannot be traced back to a person or linked from one day to the next.
Anything that would change a score. Neither you nor Credda staff can adjust anybody's number. The score is a fixed calculation over the record.
None of these views are a way to look somebody up. Credda has no lookup of a person you have no relationship with, deliberately, and nothing in the product suggests checking up on anybody. Reading the record of a stranger to decide whether to hire them is a regulated activity, and Credda is built not to be the service that supplies it.