Using a personal account for integrating Marker.io with your project management tools can lead to confusion, as updates may appear to come from a single person. To prevent this, you can:
Create a Marker.io Bot User: Set up a dedicated account (e.g., "Marker.io Bot") to centralize and clearly identify issue reports.
Let Team Members Use Their Own Accounts: Allow each team member to report issues using their individual accounts to maintain clarity.
For detailed steps on setting up a dedicated bot account, visit the full guide here on how to create a Marker.io Service Account.
Transitioning from Personal to Dedicated User
If you initially set up your integration with a personal account, shifting to a dedicated bot user is straightforward and recommended for the reasons mentioned above.
While the exact steps may differ based on the tool you're using, the general approach remains the same.
Below is how you can make this switch in Jira and will be similar for all of our integrations.
Option 2: Let Team Members Use Their Own Accounts
How It Works
Letting team members use their personal accounts allows them to report issues directly, adding flexibility and personal accountability to your workflow.
Add Team Members: Invite your team members to join your Marker.io account. This gives them the necessary access to report issues using their own integration accounts.
See a demonstration video below that walks you through these steps.
What permissions are required to integrate with our internal tools?
Administrator Access Required:
To integrate Marker.io with your internal tools, administrative credentials are generally needed. This is due to the requirement of establishing webhooks that facilitate communication with your Integration API.
The specific permissions required might vary depending on the tool you're using.
See below for advice on Jira permissions, and see the Jira guide for further details.
Need Help?
If you have any questions, comments, or corrections, chat with us at the bottom right of our web pages.