access customer portal for tickets
ART-1978_KNOWLEDGE_NODE-32
on the following URL: support.devrev.ai/<yourcompany>.\n* Your customers can log in on the portal by entering their registered email address and OTP sent to that email address.\n\n![]()\n\n### Customer roles and permissions\n\nThe customer portal has two levels of customer roles and permissions:\n\n* **Verified customers**: Customers who can log in on the portal and see the tickets that they have created.\n* **Customer admins**: Customers who can log in on the portal and see not just their own
Customer portal | Computer for Support Teams | DevRev
ART-1978_KNOWLEDGE_NODE-33
tickets but also all the tickets raised by the other users from their organization. You can add multiple customer admins from the same customer organization.\n\nOnly verified users can login into the portal.\n\nTo create a verified user:\n\n1. Go to **Accounts** in the DevRev app and create an account.\n2. Create a contact under **Contacts** and link it to the account.\n\n### Set up customer admins\n\nTo set up customer admins, follow these steps:\n\n1. Log in on your DevRev app with your
Customer portal | Computer for Support Teams | DevRev
ART-1978_KNOWLEDGE_NODE-34
registered email address and go to **Settings** > **User management** > **Groups > Customer Admins**.\n2. Select the **Add User** option in the top-right corner to search for the customer whom you want to designate as a customer admin.\n\n### Customer portal login methods\n\nThe customer portal supports three login methods:\n\n1. Email OTP (One-Time Password): User enters their email, receives a one-time code, and enters it to log in.\n2. SSO: Users log in through organization\xe2\x80\x99s
Customer portal | Computer for Support Teams | DevRev
ART-1978_KNOWLEDGE_NODE-41
If no such contact is found, JIT provisioning automatically creates a user account, allowing immediate access to the portal. This means users can sign up and log in without manual contact creation within the app.\n* **Existing contacts without mapped accounts**: If a user is already a contact within the app but does not have a mapped account, they can still log in and create a ticket. In this scenario, the login is performed under the default workspace assigned to the contact.\n* **Account
Customer portal | Computer for Support Teams | DevRev
ART-1978_KNOWLEDGE_NODE-39
toggle and craft your own title and description.\n7. Enable **Public portal** to allow unauthenticated users to view/search public articles.\n8. Click **Save & publish** to make the changes visible on your portal.\n\nIf you want to customize the font color and favicon, contact DevRev support. For favicon customization, an icon in .ico format is needed.\n\nCustomize portal URL\n--------------------\n\nBy default, your customer portal is hosted at support.devrev.ai/<yourcompany>. The
Customer portal | Computer for Support Teams | DevRev
ART-2027_KNOWLEDGE_NODE-31
to the ticket via email. They cannot view the ticket on the portal, as they are added to the **Email members** field but not to the **Reported by** field.\n\nEmployees\n\n* With DevRev account (added to email thread)\n\n  *Added to:* **To**, **CC**, or **Email members** field.\n\n  *Is able to:* View the ticket on DevRev, reply via email, and receive in-app notifications. If they make changes to ticket attributes, they remain subscribers.\n* Manually added subscribers\n\n  *Added to:*
Email | Integrate | Snap-ins | DevRev
ART-2027_KNOWLEDGE_NODE-30
or @mentioned in the DevRev app.\n\n  *Is able to:* View the ticket on the portal and reply via email as an email member.\n* A customer admin for the same workspace\n\n  *Added to:* **Customer Admins** group.\n\n  *Is able to:* View the ticket on the portal once their workspace is updated on the ticket.\n* An end user outside original sender's organization\n\n  *Added to:* **To** or **CC** fields in the email thread, or mentioned in the DevRev app (adds them to **CC**).\n\n  *Is able to:* Reply
Email | Integrate | Snap-ins | DevRev
ART-1978_KNOWLEDGE_NODE-0
b"Customer portal | Computer for Support Teams | DevRev\n\n* Computer\n* Resources\n* [Our Customers](/case-study)\n\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\n\nComputer\n\nResources\n\n[Our Customers](/case-study)\n\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\n\nSearch\n\n`CTRL`\xc2\xa0+\xc2\xa0`K`\n\n* [Introduction](/docs)\n* [Computer by DevRev](/docs/intro)\n\n  + [Core concepts](/docs/product/core)\n  + [Apps](/docs/product/apps)\n  +
Customer portal | Computer for Support Teams | DevRev
ART-2027_KNOWLEDGE_NODE-29
your communication requirements.\n\nThe visibility and interaction capabilities with a ticket in DevRev are determined by the user's role and how they were added to the email thread.\n\nEnd users\n\n* Original sender\n\n  *Added to:* **Reported by** or **Email members** field.\n\n  *Is able to:* View the ticket on the portal and reply via email.\n* An end user in the same organization\n\n  *Added to:* **To** or **CC** fields in the email thread; **Reported by** field, **Email members** field,
Email | Integrate | Snap-ins | DevRev
ART-6174_KNOWLEDGE_NODE-29
rules\n\nWorkflows enable seamless handovers from automated conversations to your support teams when necessary.\n\nPlug widget end-user experience\n-------------------------------\n\nWhen a conversation is converted to a ticket in the Plug widget:\n\n* The ticket number and basic details appear in the same conversation pane.\n* Users can click **Details** to view complete ticket information.\n* If the **Tickets** tab is enabled in Plug, users can track their ticket status
Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev