Members: Team member with access to your issue tracker (Jira, Trello, GitHub,..)
Guests: Non-technical contributors without access to your issue tracker.
Without Marker.io, these people would typically report feedback by manually logging new issues into your team's favorite tool (Trello, Jira, Github,..). They are usually part of the core product/project team.
Typical roles are project/product managers, QA testers, developers and designers.
Managers and developers who need to manage issue templates, destinations and reporter setting should be added as Admins.
Without Marker.io, these people would typically report feedback by sending emails, giving phone calls and organizing meetings. They are non-technical project stakeholders outside of the core product/project team.
Typical roles are clients, content writers, support agents, beta testers and end-users.
🔗 Integration account
Because these people have access to your team's favorite issue tracking platform (trello, asana, jira,..), they can report issues in your issue tracker via their personal integration account.
Example: Sally is a QA tester with a Jira account. By connecting her personal Jira account to her Marker.io account, she will be able to report new issue in Jira through Marker.io, while making sure that she is listed as the reporter in the Jira issue.
Because these people don't have access to your team's favorite issue tracking platform (trello, asana, jira,) they can only report feedback in your issue tracker via a team generic integration account (ex: firstname.lastname@example.org, email@example.com ) defined by admin users.
Example: John is a non-technical client who does not have a Trello account. After being invited by a project manager inside Marker.io, John will be able to report website feedback directly into the Trello board defined by the PM, without the need to have a Trello account. To identify him, his email address will be added as text in the Trello card's description.
📸 Reporting experience
Because member reporters are used to reporting inside issue trackers (trello, jira, asana, ..), they can access all reporting options that they would get inside the issue tracker. This means that they can change issue types, select labels, assign team members, attach screenshot to existing issues and much more.
Because guest reporters are used to sending emails to report feedback, their reporting experience of Marker.io is extremely simplified.
1-click capture → annotate → explain in a few words (if necessary) → send.
They don't even realize that they are reporting feedback into an integration.