ezgh sso users create <email> --name <name> [--given-name g] [--family-name f] [--department d] [flags]Create a hosted user. They’re pendingActivation until they follow the activation link EZGH SSO emails them (it works once, for 24 hours), and set a password and second factor, or a passkey, as the sign-in policy requires. The email is always sent: the API has no way to skip it. resend-activation sends a new link. Users count against the sso.users.count quota.
--department is ${user.department} in SAML attributes and outbound SCIM mappings. People from a domain routed to an identity provider don’t need creating: they get a user when they first sign in there, or when its SCIM provisions them.
Part of ezgh sso users.
Examples
ezgh sso users create ada@acme.com --name "Ada Lovelace" --department EngineeringFlags
| Flag | Type | Default | Description |
|---|---|---|---|
--department |
string | their department (${user.department} in SAML attributes and SCIM mappings) | |
--family-name |
string | their family name | |
--given-name |
string | their given name | |
--name |
string | the user’s display name |
This command also takes the global flags.