github.com/danp/terraform@v0.9.5-0.20170426144147-39d740081351/website/source/docs/providers/pagerduty/r/user.html.markdown (about) 1 --- 2 layout: "pagerduty" 3 page_title: "PagerDuty: pagerduty_user" 4 sidebar_current: "docs-pagerduty-resource-user" 5 description: |- 6 Creates and manages a user in PagerDuty. 7 --- 8 9 # pagerduty\_user 10 11 A [user](https://v2.developer.pagerduty.com/v2/page/api-reference#!/Users/get_users) is a member of a PagerDuty account that have the ability to interact with incidents and other data on the account. 12 13 14 ## Example Usage 15 16 ```hcl 17 resource "pagerduty_team" "example" { 18 name = "Engineering" 19 description = "All engineering" 20 } 21 22 resource "pagerduty_user" "example" { 23 name = "Earline Greenholt" 24 email = "125.greenholt.earline@graham.name" 25 teams = ["${pagerduty_team.example.id}"] 26 } 27 ``` 28 29 ## Argument Reference 30 31 The following arguments are supported: 32 33 * `name` - (Required) The name of the user. 34 * `email` - (Required) The user's email address. 35 * `color` - (Optional) The schedule color for the user. 36 * `role` - (Optional) The user role. Account must have the `read_only_users` ability to set a user as a `read_only_user`. Can be `admin`, `limited_user`, `owner`, `read_only_user`, `team_responder` or `user` 37 * `job_title` - (Optional) The user's title. 38 * `teams` - (Optional) A list of teams the user should belong to. 39 * `description` - (Optional) A human-friendly description of the user. 40 If not set, a placeholder of "Managed by Terraform" will be set. 41 42 ## Attributes Reference 43 44 The following attributes are exported: 45 46 * `id` - The ID of the user. 47 * `avatar_url` - The URL of the user's avatar. 48 * `html_url` - URL at which the entity is uniquely displayed in the Web app 49 * `invitation_sent` - If true, the user has an outstanding invitation. 50 51 ## Import 52 53 Users can be imported using the `id`, e.g. 54 55 ``` 56 $ terraform import pagerduty_user.main PLBP09X 57 ```