unable to open a ticket error
ART-1955_KNOWLEDGE_NODE-28
tickets.\n\n  Privileges: ticket object ['CREATE']\n* *Customer Ticket Field Access:* Contains the field access on tickets\n\n  Privileges: ticket object None\n* *Self RevOrg Viewer:* Contains privileges on revOrgs for revUsers to view there workspace.\n\n  Privileges: revo object ['READ']\n* *Self RevOrg RevUsers Viewer:* Contains privileges on revUsers for revUsers to view there workspace revUsers.\n\n  Privileges: revu object ['READ']\n* *Self RevUsers Viewer:* Contains privileges on
Default privileges by group | Roles | Computer by DevRev | DevRev
ART-1978_KNOWLEDGE_NODE-38
conversations on the portal.\n3. Under **Styling**, upload a banner image which should be in the ratio of 6:1. You can also set light/dark mode for appearance and select your accent color.\n4. If you want to enable customers to create tickets from the portal, under **Tabs** turn on **Enable ticket creation**. Assign default owner and part.\n5. If you want to enable public ticket creation wherein unauthenticated users can create tickets, contact DevRev support.\n6. Turn on the **Enable banner**
Customer portal | Computer for Support Teams | DevRev
ART-4255_KNOWLEDGE_NODE-33
\n**Solution** : Confirm that user identification is performed before using the `showSupport()` function or XML button.\n\n  * **Issue** : Incorrect operation due to `App ID` and `secret` misconfiguration.  \n**Solution** : Ensure correct functionality by double-checking that both `App ID` and `secret` values are accurately configured in your application or sample app.\n\nWas this page helpful?YesNo\n\n[DevRev SDK for iOSUp Next](/public/sdks/ios)\n\n[Built
DevRev SDK for Android — DevRev | Docs
ART-1955_KNOWLEDGE_NODE-89
object ['READ', 'UPDATE']\n* *Ticket Creator:* Contains create privileges on tickets.\n\n  Privileges: ticket object ['CREATE']\n* *RevUser ticket Admin:* Contains privileges on user tickets admins.\n\n  Privileges: ticket object ['READ', 'UPDATE']\n* *RevUser conversation Admin:* Contains privileges on conversation admins.\n\n  Privileges: conversation object ['READ', 'UPDATE']\n\n\xe2\x80\x9cDev Users\xe2\x80\x9d group\n-----------------\n\nGroup for all dev users.\n\n**Privileges:**\n\n*
Default privileges by group | Roles | Computer by DevRev | DevRev
ART-1483_KNOWLEDGE_NODE-4
changes to the snap-in:\n\n  1. Update the trigger condition to run every 10 minutes instead of work creation.\n  2. Create a ticket whenever the snap-in is triggered.\n\nEnsure that you have at least one [part](https://docs.devrev.ai/product/parts#product-or-service) in your organization since every ticket must be linked to a part and have an owner.\n\nSince a DevRev ticket is created whenever the function is triggered, DevRev APIs need to be called that allow this functionality. Although one
Using a snap-in to perform a DevRev action — DevRev | Docs
ART-1958_KNOWLEDGE_NODE-27
of all the roles associated with the target. If at least one role provides the necessary privilege, say create privilege, the actor is granted permission to proceed with the action, allowing them to create the issue.\n\n```\nGroups\n\n\n\nGroups\n\n\n\nUser\n\n\n\nEngineering\n\n\n\nSupport\n\n\n\nRole READ on parts\n\n\n\nRole CREATE on tickets\n\n\n\nCREATE on tickets  \nREAD on parts\n```\n\nIf a user attempts an action they\'re not authorized to perform, they see a message which says "You
Access control | Computer by DevRev | DevRev