Uptimeify Docs
Resources

uptimeify_user

A login of the organization. Creating it sends an invitation mail; the person sets their own password (Terraform never sets one). Destroying it deletes the login. Needs an organization admin token. Import with the user id.

A login of the organization. Creating it sends an invitation mail; the person sets their own password (Terraform never sets one). Destroying it deletes the login. Needs an organization admin token. Import with the user id.

Example Usage

# Sends an invitation mail; the person sets their own password.
resource "uptimeify_user" "ops" {
  email      = "ops@example.com"
  first_name = "Olivia"
  last_name  = "Ops"
  role       = "editor"
}

# A customer login, limited to one customer.
resource "uptimeify_user" "shop_owner" {
  email        = "owner@shop.example"
  role         = "readonly"
  customer_ids = [12]
  language     = "en"
}

Schema

Required

  • email (String) Login address. Changing it invites a new login (replacement).
  • role (String) admin, editor, readonly or responder.

Optional

  • customer_ids (Set of Number) Customers a readonly login is limited to (customer user). Empty = all customers. Only allowed with role = "readonly".
  • first_name (String)
  • is_active (Boolean) false deactivates the login without deleting it.
  • language (String) Language of the login (dashboard, mails, SMS): de, en or da; null = organization language. Always read from the API, so a language the person picks in their profile shows as drift. A change is sent in place (PATCH); removing it from the configuration keeps the current language.
  • last_name (String)

Read-Only

  • created_at (String)
  • id (String) User id, as user_id in IM resources.
  • name (String) Display name the server derives from first and last name.

Import

Import is supported using the following syntax:

The terraform import command can be used, for example:

# User id
terraform import uptimeify_user.ops 3f1c0a8e-...

On this page