Optionaldata: ITrusteeSecurityOptionalauditThe audit classes configured for the trustee, split into successful- and failed-operation masks. Each map is keyed by audit-class name with the value indicating whether that class is audited.
OptionalfeatureThe trustee's feature rights, keyed by feature-right name (e.g. Search, Import), with the value indicating whether the trustee holds that feature right.
OptionalisTrue when the trustee is read-only, so no write operations are possible regardless of the granted privileges or feature rights.
OptionalprivilegesThe trustee's privileges, keyed by privilege name (e.g. EntryAccess, RecordManager), with the value indicating whether the trustee holds that privilege.
OptionaltagsThe security tags assigned to the trustee.
Optional_data: anyOptionaldata: anyStaticfromJS
A trustee's account security: the privileges and feature rights the trustee holds, the security tags assigned to it, the audit classes configured for it, and whether the trustee is read-only. Privileges, feature rights, and audit masks are reported as named booleans (each map keyed by the right's name with a granted true/false) rather than raw bitmasks. The values are either effective (the default — what applies once the trustee's group memberships are resolved) or direct (only what is assigned on the trustee record itself), selected by the request's includeInherited flag. The effective view is a documented best-effort computation: in rare cases it can differ from the trustee's real rights. The authoritative way to determine a trustee's security is to sign in as that trustee and read the resulting session's rights.