[{"data":1,"prerenderedAt":37},["Reactive",2],{"featurePages":3,"blogPosts-team-permissions":4},[],{"slug":5,"id":6,"uuid":7,"title":8,"html":9,"comment_id":6,"feature_image":10,"featured":11,"visibility":12,"created_at":13,"updated_at":14,"published_at":15,"custom_excerpt":10,"codeinjection_head":10,"codeinjection_foot":16,"custom_template":10,"canonical_url":10,"tags":17,"authors":24,"primary_author":31,"primary_tag":32,"url":33,"excerpt":34,"reading_time":35,"access":36,"comments":11,"og_image":10,"og_title":10,"og_description":10,"twitter_image":10,"twitter_title":10,"twitter_description":10,"meta_title":10,"meta_description":10,"email_subject":10,"frontmatter":10,"feature_image_alt":10,"feature_image_caption":10},"team-permissions","64caa4c4730b190d1c2da6e3","04e8a38a-3a61-416e-bce1-ed7baadd4469","Updating team permissions","\u003Cp>Some of our customers have experienced confusion and broken workflows due to the way Chatwoot manages permissions. In response, we are updating the permission structure.\u003C/p>\u003Cp>\u003Cstrong>The existing structure\u003C/strong>\u003C/p>\u003Cp>Currently, agent permissions are assigned directly to inboxes. To access a conversation, an agent must be added to the corresponding channel inbox. Even if an agent is part of a team, they will not have access to conversations until they are added to the respective inbox. This has made it difficult to manage permissions for different teams. For instance, the billing team is only concerned with billing-related issues and does not want to see other conversations. Moreover, it forces people to add every agent to every inbox.\u003C/p>\u003Cp>\u003Cstrong>The updated structure\u003C/strong>\u003C/p>\u003Cp>In the new structure, conversation access will be assigned to teams, along with individual agents. This means that if an agent is part of a team assigned to a conversation, they will automatically have access to that conversation without needing to be manually added to the inbox. This simplifies the process of managing permissions for different teams and streamlines workflows.\u003C/p>\u003Cp>\u003Cstrong>How does the assignment work here?\u003C/strong>\u003C/p>\u003Cp>Previously, the dropdown only showed the list of people who had access to the inbox (including administrators). With the latest change, it now shows the list of people who have access to the team as well.\u003C/p>\u003Cp>\u003Cstrong>Does the round robin assignment work for the new flow?\u003C/strong>\u003C/p>\u003Cp>Yes, it would. Even if you are not directly part of the inbox, as long as the team is assigned to the conversation, the round-robin assignment will work as usual.\u003C/p>\u003Cp>\u003Cstrong>Do you lose access if the conversation is assigned to another team?\u003C/strong>\u003C/p>\u003Cp>Currently, yes. If the conversation gets reassigned to another team, you would lose access.\u003C/p>\u003Cp>However, we will be updating this based on participant permission. If you are from another team and have been added as a participant, you should be able to view the conversation without any issues going forward.\u003C/p>\u003Cp>Feel free to reach out to us if you have any questions or concerns.\u003C/p>",null,false,"public","2023-08-02T18:47:32.000+00:00","2026-07-07T13:55:41.000+00:00","2023-08-02T18:53:38.000+00:00","ссс",[18],{"id":19,"name":20,"slug":20,"description":21,"feature_image":10,"visibility":12,"og_image":10,"og_title":10,"og_description":10,"twitter_image":10,"twitter_title":10,"twitter_description":10,"meta_title":10,"meta_description":10,"codeinjection_head":10,"codeinjection_foot":10,"canonical_url":10,"accent_color":22,"url":23},"6118da7b4b8f26503f72d52e","releases","We release a new and improved version of Chatwoot every mid-month. We make sure to tell you all about it and how you can use it to improve your Chatwoot experience, in our series of product updates.","#189aff","https://www-internal-blog.chatwoot.com/tag/releases/",[25],{"id":26,"name":27,"slug":28,"profile_image":29,"cover_image":10,"bio":10,"website":10,"location":10,"facebook":10,"twitter":10,"meta_title":10,"meta_description":10,"threads":10,"bluesky":10,"mastodon":10,"tiktok":10,"youtube":10,"instagram":10,"linkedin":10,"url":30},"69f9f0829254f3684b76f52a","Pranav Raj S","pranav","https://www-internal-blog.chatwoot.com/content/images/2023/08/2246121.jpeg","https://www-internal-blog.chatwoot.com/author/pranav/",{"id":26,"name":27,"slug":28,"profile_image":29,"cover_image":10,"bio":10,"website":10,"location":10,"facebook":10,"twitter":10,"meta_title":10,"meta_description":10,"threads":10,"bluesky":10,"mastodon":10,"tiktok":10,"youtube":10,"instagram":10,"linkedin":10,"url":30},{"id":19,"name":20,"slug":20,"description":21,"feature_image":10,"visibility":12,"og_image":10,"og_title":10,"og_description":10,"twitter_image":10,"twitter_title":10,"twitter_description":10,"meta_title":10,"meta_description":10,"codeinjection_head":10,"codeinjection_foot":10,"canonical_url":10,"accent_color":22,"url":23},"https://www-internal-blog.chatwoot.com/team-permissions/","Some of our customers have experienced confusion and broken workflows due to the way Chatwoot manages permissions. In response, we are updating the permission structure.\n\nThe existing structure\n\nCurrently, agent permissions are assigned directly to inboxes. To access a conversation, an agent must be added to the corresponding channel inbox. Even if an agent is part of a team, they will not have access to conversations until they are added to the respective inbox. This has made it difficult to ma",1,true,1784765399118]