Skip to main content
Reputation in Sublay is space-scoped. Instead of a single number per user, each user accrues reputation into separate buckets — one per space, plus a project-general bucket — and their reputation field is the maintained sum of all of them. Reputation is owned by the optional reputation bundle. Install it from the Database page of your project to turn the feature on. The reputation bundle works with or without the spaces bundle: without spaces, only the general bucket accrues. See Bundles.

​
Buckets

The bundle provisions a per-tenant table of reputation buckets, keyed by (userId, spaceId).
BucketKeyMeaning
Project-generalspaceId IS NULLThe user’s reputation outside of any space.
Per-spacespaceId = <spaceId>The user’s reputation within that specific space.
A few rules govern buckets:
  • Lazy creation — a bucket is created the first time a user’s reputation changes for that (user, space) pair. A bucket that has never been touched reads as 0.
  • Negative scores allowed — there is no floor; a bucket can go below zero.
  • Buckets are not returned directly — there is no endpoint that lists raw buckets. You read reputation through the reputation total and the opt-in spaceReputation field described below.

​
The maintained total

Every user object still carries a reputation field, and default API responses are unchanged. reputation is the maintained overall total — the sum of all of that user’s buckets (general plus every space). It is always present, whether or not a space is in context.

​
Reading space-scoped reputation

Every user-returning endpoint accepts an opt-in spaceReputation object that adds a spaceReputation number to each returned user. The reputation total is always included regardless; the per-space spaceReputation field is purely additive and only appears when you ask for it.

​
The spaceReputation object (primary form)

Pass a single object. Its two fields express which bucket to read and whether to sum descendants: 
spaceReputation: {
  spaceId: string | "none" | "context"; // "context" only on context endpoints
  includeDescendants?: boolean;
}
​
spaceReputation
object
Opt-in. Adds a spaceReputation number to each returned user, scoped to a single space.
The object has two variants depending on the endpoint class — they differ only in whether spaceId accepts "context":
VariantspaceId acceptsUsed by
Context<uuid> · "none" · "context"Entities, comments, reactions, chat, space members/team, moderated reports, content search & ask
User-direct<uuid> · "none"Fetch user (by ID / foreign ID / username), user suggestions, followers/following/connections by user ID

​
Deprecated flat props

The object replaces two flat props that travelled together. They still work — passing the object wins if both forms are supplied — but they are deprecated and will be removed in a later major version. Prefer the object.
​
spaceReputationId
string
deprecated
Deprecated — use spaceReputation.spaceId. Same value set as the object’s spaceId for the matching endpoint variant (<uuid> / "none", plus "context" on context endpoints only).
​
spaceReputationDescendants
boolean
deprecated
Deprecated — use spaceReputation.includeDescendants. Only honored alongside an explicit spaceReputationId <uuid>.
The resulting field appears on each user object as:
​
spaceReputation
number
The user’s reputation in the requested space (or the space-less bucket). Present only when the spaceReputation object (or the deprecated spaceReputationId) was supplied. Missing buckets read as 0.

​
Where the params apply

The spaceReputation object is accepted on every user-returning endpoint, but the allowed values for spaceId depend on whether the endpoint has a space in context. Context endpoints accept <uuid>, none, and context:
  • Entity feed and single entity
  • Comment feed and single comment
  • Entity and comment reaction lists
  • Chat — list messages, get message, send message, list members, list reactions
  • Space members and space team
  • Moderated reports
  • Content search and AI ask
User-direct endpoints accept <uuid> and none only — context is rejected (400) because there is no space context to derive:
  • Fetch user (by ID, foreign ID, or username) and user suggestions
  • Followers / following lists (by user ID)
  • Connections list (by user ID)
Project-wide user search (search-users) and the self-relative follows/connections lists are not enriched and ignore the param.

​
Uninstalling is lossy

Removing the reputation bundle drops the buckets table and zeroes the reputation column on every user. Reinstalling starts fresh from zero — past scores are not recomputed. Back up anything you need before uninstalling. See Bundles.

​
See Also