{"_id":"593878f4682adc0031784c07","category":{"_id":"593878f2682adc0031784bf5","version":"593878f2682adc0031784bf3","project":"55f0757d4624ec2d00814345","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-09-09T21:17:41.905Z","from_sync":false,"order":1,"slug":"tigerconnect-basics","title":"Basics"},"parentDoc":null,"project":"55f0757d4624ec2d00814345","user":"55f0756a1e63fc37004b8d2b","version":{"_id":"593878f2682adc0031784bf3","project":"55f0757d4624ec2d00814345","__v":1,"createdAt":"2017-06-07T22:06:42.610Z","releaseDate":"2017-06-07T22:06:42.610Z","categories":["593878f2682adc0031784bf4","593878f2682adc0031784bf5","593878f2682adc0031784bf6","593878f2682adc0031784bf7","593878f2682adc0031784bf8","593878f2682adc0031784bf9","593878f2682adc0031784bfa","593878f2682adc0031784bfb"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"3.0.0","version":"3"},"__v":0,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2015-09-09T21:52:57.094Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":2,"body":"A User represents a single account. Sending a message to a User results in a message only to that user which we sometimes refer to as a peer-to-peer (P2P) conversation.  \n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Profile\"\n}\n[/block]\nEach TigerText [User](doc:messaging-users-and-groups) can control various aspects of their account.  This includes profile information such as their name, avatar, department, title and current status message.  \n\nIn addition to profile information, [User](doc:messaging-users-and-groups) can turn on the Do Not Disturb (DND) setting.  When DND is turned on, all P2P messages that they receive will get an automatic response that the [User](doc:messaging-users-and-groups) has set.  To prevent the auto response from firing too often, only the first message triggers a response.   \n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Addressing Users\"\n}\n[/block]\nUsers can be addressed by either email address, phone number or user token.   To differentiate between the different types of identification, we use an addressing schema which are evaluated in the following order:\n\n**Email Address**\n<li><b>Rule:</b> If an address contains exactly one :::at::: and this @ is not its first character, it represents an email address</li>\n<li><b>Regular Expression:</b> [^@]+[@][^@]*</li>\n<li><b>Example:</b> myemail@address.com tells the server to locate the user with email_address = \"myemail@address.com\"</li>\n\n**Phone Number**\n<li><b>Rule:</b> If an address starts with +, it represents a phone number</li>\n<li><b>Regular Expression:</b> [+].*</li>\n<li><b>Example:</b> +13105551212 tells the server to locate the user with phone_number = *\"+13105551212\" </li>\n[block:callout]\n{\n  \"type\": \"info\",\n  \"body\": \"Note: Don't forget to properly url encode your phone numbers. In a url, for instance, +13105551212 should become %2B13105551212\",\n  \"title\": \"Remember to encode\"\n}\n[/block]\n\"User Token\"\n<li><b>Rule:</b> Anything that doesn't match any of the previous rules, represents a token</li>\n<li><b>Regular Expression:</b> .*</li>\n<li><b>Example:</b> 3575f3ae-86e2-4d60-b719-fc6effcb7a0b tells the server to locate the user with token = \"3575f3ae-86e2-4d60-b719-fc6effcb7a0b\"</li>\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"User Roles\"\n}\n[/block]\nEach TigerText [User](doc:messaging-users-and-groups) can also be assigned additional roles depending on their permissions and who they are allowed to message.  \n\n**Regular**\nThis is the default user role.  \n-  Organization management:  This User does not have the permissions to add or remove other Users from the organization. \n-  Sending messages:  This users is able to send messages to all other users in the organization. \n\n**Admin Role**\nThe Admin user role has elevated organization management permissions. \n-  Organization management:  This User has permissions to add or remove other Users from the [Organization](doc:organizations). \n-  Sending messages:  This User is able to send messages to all other Users in the [Organization](doc:organizations). \n\n**Customer Role**\nThe Customer user role has limited organization management permissions and limited message sending permissions. \n-  Organization management:  This User does not have the permissions to add or remove other Users from the organization. \n-  Sending messages:  This User is not able to send messages to other Customer Users in the [Organization](doc:organizations).  They are allowed to send messages to Admin and Regular Users in the [Organization](doc:organizations).","excerpt":"","slug":"messaging-users-and-groups","type":"basic","title":"Users"}
A User represents a single account. Sending a message to a User results in a message only to that user which we sometimes refer to as a peer-to-peer (P2P) conversation. [block:api-header] { "type": "basic", "title": "Profile" } [/block] Each TigerText [User](doc:messaging-users-and-groups) can control various aspects of their account. This includes profile information such as their name, avatar, department, title and current status message. In addition to profile information, [User](doc:messaging-users-and-groups) can turn on the Do Not Disturb (DND) setting. When DND is turned on, all P2P messages that they receive will get an automatic response that the [User](doc:messaging-users-and-groups) has set. To prevent the auto response from firing too often, only the first message triggers a response. [block:api-header] { "type": "basic", "title": "Addressing Users" } [/block] Users can be addressed by either email address, phone number or user token. To differentiate between the different types of identification, we use an addressing schema which are evaluated in the following order: **Email Address** <li><b>Rule:</b> If an address contains exactly one @ and this @ is not its first character, it represents an email address</li> <li><b>Regular Expression:</b> [^@]+[@][^@]*</li> <li><b>Example:</b> myemail@address.com tells the server to locate the user with email_address = "myemail@address.com"</li> **Phone Number** <li><b>Rule:</b> If an address starts with +, it represents a phone number</li> <li><b>Regular Expression:</b> [+].*</li> <li><b>Example:</b> +13105551212 tells the server to locate the user with phone_number = *"+13105551212" </li> [block:callout] { "type": "info", "body": "Note: Don't forget to properly url encode your phone numbers. In a url, for instance, +13105551212 should become %2B13105551212", "title": "Remember to encode" } [/block] "User Token" <li><b>Rule:</b> Anything that doesn't match any of the previous rules, represents a token</li> <li><b>Regular Expression:</b> .*</li> <li><b>Example:</b> 3575f3ae-86e2-4d60-b719-fc6effcb7a0b tells the server to locate the user with token = "3575f3ae-86e2-4d60-b719-fc6effcb7a0b"</li> [block:api-header] { "type": "basic", "title": "User Roles" } [/block] Each TigerText [User](doc:messaging-users-and-groups) can also be assigned additional roles depending on their permissions and who they are allowed to message. **Regular** This is the default user role. - Organization management: This User does not have the permissions to add or remove other Users from the organization. - Sending messages: This users is able to send messages to all other users in the organization. **Admin Role** The Admin user role has elevated organization management permissions. - Organization management: This User has permissions to add or remove other Users from the [Organization](doc:organizations). - Sending messages: This User is able to send messages to all other Users in the [Organization](doc:organizations). **Customer Role** The Customer user role has limited organization management permissions and limited message sending permissions. - Organization management: This User does not have the permissions to add or remove other Users from the organization. - Sending messages: This User is not able to send messages to other Customer Users in the [Organization](doc:organizations). They are allowed to send messages to Admin and Regular Users in the [Organization](doc:organizations).