Can support look at or enter my console to diagnose an issue?

We're always glad to help investigate a tricky issue, and the cleanest way is for you to share what we need rather than hand over your password. Scoped access keeps your account safe while still letting us dig into the problem.

How we help safely

Most issues are diagnosable from your logs alone, so sharing those is the fastest first step. When we do need hands-on access, subuser permissions let us in with exactly the scope required — and you can revoke it the moment we're done.

How to give us access

1. Share your logs first — most issues are diagnosable from an mclo.gs link alone.
2. If we need hands-on access, add us as a subuser on the Sub-users page with the permissions the task needs (see "How do I add someone without sharing my password?").
3. Remove the subuser access again once the issue is resolved.

Warning: Never share your panel password. Subuser access is safer, scoped, and revocable.

Frequently asked questions

What permissions should I grant? Console and Files access usually suffice for diagnostics — enough for us to see what's happening and check the relevant files.

Can you fix it directly? Often yes, once we can see the console and files through scoped subuser access.