{  "classifications": [    {      "name": "string",      "description": "string",      "sessionTimeLimitRule": "SESSION_TIME_LIMIT_RULE_UNSPECIFIED",      "accessAllTenants": true,      "maxConcurrentSessions": 0,      "createdTime": 0,      "modifiedTime": 0,      "version": 0    }  ]}

export interface Response {classifications?: SessionClassification[]}/** * SessionClassification is a named set of session rules applied to the users assigned to it. The name is *  the id: unique per project and immutable. */export interface SessionClassification {name: stringdescription?: string/** * How a member's session time limit is decided. *   SESSION_TIME_LIMIT_RULE_UNSPECIFIED (0, the default) means the group does not override it, so *   members are treated like a user with no group at all. *   SESSION_TIME_LIMIT_RULE_MIN_OF_TENANTS (1) uses the shortest limit among all the tenants the *   user belongs to. *   SESSION_TIME_LIMIT_RULE_PROJECT_SETTINGS (2) inherits the project-wide session time limit. *   SESSION_TIME_LIMIT_RULE_CURRENT_TENANT (3) follows the limit of the tenant the session is *   currently in, so it changes with the tenant context rather than being fixed at sign-in. */sessionTimeLimitRule?: ("SESSION_TIME_LIMIT_RULE_UNSPECIFIED" | "SESSION_TIME_LIMIT_RULE_MIN_OF_TENANTS" | "SESSION_TIME_LIMIT_RULE_PROJECT_SETTINGS" | "SESSION_TIME_LIMIT_RULE_CURRENT_TENANT")/** * Members may access every tenant in the project regardless of their explicit assignments */accessAllTenants?: boolean/** * Overrides the project-wide limit for members, in both directions. 0 means UNLIMITED: it *  lifts the project cap for members rather than inheriting it. */maxConcurrentSessions?: number/** * Computed server side: accepted and ignored on write, so a read response can be sent back as an *  update. Epoch seconds as int32, matching every other createdTime/modifiedTime in this file: *  protobuf JSON renders a 64-bit integer as a quoted string. */createdTime?: numbermodifiedTime?: number/** * The revision this group was read at. Send it back on an update and the write is rejected with *  a conflict if someone else changed the group in the meantime. Omit it to update regardless of *  who wrote last. */version?: number}