DescribeUserResponse

import type { DescribeUserResponse } from "https://aws-api.deno.dev/v0.3/services/workmail.ts?docs=full";

interface DescribeUserResponse {

DisabledDate?: Date | number | null;

DisplayName?: string | null;

Email?: string | null;

EnabledDate?: Date | number | null;

Name?: string | null;

State?: EntityState | null;

UserId?: string | null;

UserRole?: UserRole | null;

}

§Properties

DisabledDate?: Date | number | null

[src]

The date and time at which the user was disabled for Amazon WorkMail usage, in UNIX epoch time format.

DisplayName?: string | null

[src]

The display name of the user.

Email?: string | null

[src]

The email of the user.

EnabledDate?: Date | number | null

[src]

The date and time at which the user was enabled for Amazon WorkMail usage, in UNIX epoch time format.

Name?: string | null

[src]

The name for the user.

State?: EntityState | null

[src]

The state of a user: enabled (registered to Amazon WorkMail) or disabled (deregistered or never registered to WorkMail).

UserId?: string | null

[src]

The identifier for the described user.

UserRole?: UserRole | null

[src]

In certain cases, other entities are modeled as users. If interoperability is enabled, resources are imported into Amazon WorkMail as users. Because different WorkMail organizations rely on different directory types, administrators can distinguish between an unregistered user (account is disabled and has a user role) and the directory administrators. The values are USER, RESOURCE, and SYSTEM_USER.