Collect website feedback as new issues directly in your GitHub projects. Issue status and fields stay in sync automatically. See the note on comment sync below for how communication works.
Set up a GitHub integration
Add a project
To get started, go to the Marker.io dashboard and create a project. Complete the project form:
Project name
Website URL: the site where you wish to collect feedback
Integration: select GitHub
Space: the space within GitHub where you wish to receive feedback
If this is your first time connecting, you need to authorize Marker.io to use your GitHub account.
Configure forms
Marker.io fetches your native GitHub fields into your widget form. You can show/hide fields and preset values. For example, set the Labels field to Bug so all new feedback gets flagged automatically.
Note: Marker.io members report through the Member form, while Guests and Public Reporters report via the Guest form. More on that in our User Roles: Admins, Managers, Members, Guests & Reporters guide.
Manage project access
Separately from your GitHub connection, Marker.io controls who can see and manage feedback for this project via Manage access (top-right of the project's Widget or Feedback view).
Two ways to grant access:
Groups > Workspace members: toggle this on to give everyone in your Marker.io workspace access at once
People: invite individuals one at a time. Each can be removed independently. Guest-level users show a GUEST badge next to their name, distinguishing them from full members in the list.
Admins always have access regardless of this setting. This is separate from your GitHub project access covered in Permissions & troubleshooting below: someone can have full access in Marker.io without access to the underlying GitHub project, or the other way around.
Install widget
Go to your project's Widget > Installation and choose how to install.
Tip: click Try on demo website first to test-drive the widget before installing anything on your real site.
Browser extension: quick setup, no code required. Each reporter installs the extension individually. You can also toggle "Inject widget on my website" per domain to show it automatically for extension users on that site.
Code snippet & CMS plugins: a one-time, site-wide install, accessible to all reporters. Sub-tabs cover Code snippet (paste into the
<HEAD>tag), NPM package, CMS plugins, and Send to developer (one-click handoff).
AI coding agent: point your AI coding agent at this and it picks the right install method (npm, snippet, or CMS plugin) and wires it up for you.
Visit your website, refresh, and check that the widget appears. If you used the browser extension method, remember: each reporter needs the extension installed in their own browser before they can see the widget. It won't appear for reporters who haven't installed it.
How it works
Collect feedback
Reporters can submit feedback directly to your GitHub project without leaving their website. Their feedback automatically includes detail-rich technical data.
Say the Contact Us button is broken on the About Us page. The reporter clicks the widget and is presented with a screenshot and a feedback form to complete. The screenshot can be annotated, and the form can be as simple or as complex as you wish. We recommend keeping it simple for non-technical reporters.
Review issues
In your GitHub project, feedback arrives with the screenshot and automatically captured technical data, including:
Page URL
Browser
Screen size
Operating system
Communicate with reporters
The "Contact via Marker.io" link opens the Feedback Page, where you can reply to the reporter. Marker.io pushes your replies into GitHub as comments, but comments made directly on the GitHub issue don't sync back to Marker.io. This integration follows the same one-way (from Marker.io to GitHub) comment pattern as our other integrations. Always reply from the Feedback Page if you need the reporter to see it.
Synchronize status
Once you update an issue status to "Done" in GitHub, Marker.io automatically updates the status to Resolved and emails the reporter to let them know.
Permissions & troubleshooting
Is Marker.io secure?
We take your data and the security of our systems seriously, using industry-standard security practices to connect with your account. See our latest security policy at marker.io/security.
What permissions are required to integrate with GitHub?
Admin permissions are required on the GitHub project you wish to connect with. If the connected account is later removed from the project, or its role is downgraded, sync will silently stop working. This is the most common cause of "issues stopped syncing" reports.
We recommend creating a dedicated Marker.io Bot user in GitHub rather than connecting a personal account, so sync doesn't break when an individual leaves the team or changes roles. See [[Create a Service Account or Dedicated User for your integration]].
Issues not syncing to GitHub
If issues have stopped appearing in your GitHub project, including after moving your organization to a GitHub Enterprise account:
Check that the GitHub account connected to Marker.io still has access to the target repository.
Confirm the account's role hasn't been downgraded below what's needed to create/update issues.
Go to your Marker.io project's Settings > Integration and click Resync account.
Submit a test issue and confirm it appears in GitHub.
I can't connect my GitHub account to Marker.io
Try the following, in order:
Log in to GitHub in a second tab. This ensures your username and password don't trigger extra security verification. Once logged in, return to Marker.io and try connecting again.
Reset your GitHub password, then attempt to reconnect.
Still stuck? Start a chat with us using the icon in the lower right corner.
How to enable GitHub Organization Projects (beta)
Make sure you have access to GitHub Projects:
Check your permissions on your Org Projects. You need Read and Write access to org, and organization access needs to be enabled
To grant Read and Write access, resync your GitHub account from your Marker.io shared account settings: Settings > Workspace > Shared accounts.
You should then be able to load your Organization projects and add Marker.io issues to them using the Project field.
I can't access all of my GitHub organizations
If you have more than one GitHub organization, make sure Marker.io has been granted access to all of them at github.com/settings/applications. Click Marker.io and grant access to any organization you want Marker.io to reach.
I can't disconnect my GitHub account from Marker.io
Disconnecting requires two steps:
Disconnect GitHub inside Marker.io: go to your workspace settings > Personal > Accounts, and disconnect your GitHub account.
Revoke Marker.io access inside GitHub: log into GitHub, go to your applications settings, and revoke the Marker.io app at github.com/settings/applications.
You should then be able to connect a new GitHub account.
Invite your team to collaborate on a dedicated GitHub project today with Marker.io, where anyone can report bugs and feedback in seconds. See [[Get started with Marker.io]] for more on getting the most out of your setup.
Need Help?
If you have any questions, comments, or corrections, chat with us at the bottom right of our web pages.