Kreskio guide for teams

What is Kreskio?

Kreskio is a tool for reporting bugs and feedback right on the website. Instead of emails with screenshots and descriptions like “something is broken on my phone”, you get a complete report: the marked part of the page, a description and technical details such as the browser, system and window size.

• Your clients send feedback with the “Report a bug” button on the website, without creating an account.
• Your team can report bugs on any website with the Chrome extension.
• All reports land in one place, where you can assign them, set a due date, comment and close them.
• Clients and the team can also share ideas. They go separately to the “Ideas” tab, where you vote on them and decide what to do.

Getting started

1. 1

   Create an account

   Sign up and confirm your email address by clicking the link in the message from Kreskio.

2. 2

   Create a workspace

   Enter the name of your company or team. You can also enter the address of the website you want to collect reports from, and Kreskio will create your first project.

3. 3

   Paste the code into the website

   Copy one line of code from the project page and paste it into the client’s website. You will find the details in the “Installing on the website” section.

4. 4

   Invite your team

   In the “Team” tab, invite the people who will handle reports.

5. 5

   Send the guide to your client

   On the project page you will find a link to the client guide. Send the link or download the guide as a PDF.

Workspaces

A workspace is your company or team in Kreskio. It holds your projects and team members. One account can belong to many workspaces, for example your own agency and the workspace of a client who invited you to work with them.

• Switch workspaces with the switcher in the top left corner, below the logo.
• Create a new workspace from the same menu by choosing “New workspace”.
• Rename the workspace in “Settings” (available to the owner and administrators).
• There you can also add a logo (PNG or JPG) and a brand colour. Your clients will see them in the client portal, in emails about their reports and on the “Report a bug” button on your websites – instead of the Kreskio brand.

Projects

A project is one website or app you collect reports from, for example a client’s online shop or its staging version. Each project has its own installation code and a list of allowed domains.

1. 1

   Add a project

   Go to “Projects”, click “New project” and enter the name and domain of the website.

2. 2

   Set the allowed domains

   The widget only accepts reports from websites on the list. This way nobody can use your code on someone else’s website.

3. 3

   Turn the widget off if needed

   In the project settings you can temporarily hide the report button without removing the code from the website.

4. 4

   Enter the local version address (optional)

   If you make fixes on your own copy of the website, e.g. sklep.test, enter its address in the project settings. Tasks from “Copy for AI” will then point to the reported page at that address straight away.

5. 5

   Adjust the report button (optional)

   In the “Report button” card you choose its position (bottom right or bottom left corner, or a tab on the edge when the corner is taken by a chat or cookie bar), its size and its look: an icon with a label, or just an icon that shows the label on hover. The preview next to it shows the result before you save. On 4K monitors the button gets a little bigger on its own. You can also turn on the Alt+Shift+K shortcut (Option+Shift+K on a Mac), which opens a report with a screenshot right away. Changes show up on the website after you refresh it.

6. 6

   Turn on ideas (optional)

   Tick “Take ideas in the widget” and clients will choose “Bug” or “Idea” when sending. The option is off by default, so clients will not see any change until you tell them about it. Details in the “Ideas” section.

7. 7

   Turn on revision rounds (optional, Agency plan)

   Tick “Count revision rounds” and enter how many rounds you agreed with the client. Details in the “Revision rounds” section.

Installing on the website

You will find the installation code on the project page and copy it with the “Copy” button. It consists of two <script> tags: the short first one records console errors from the moment the page starts loading, and the second one loads the widget. In short, it looks like this:

<script>(function (w) { … })(window);</script>
<script type="module" src="https://kreskio.pl/widget/v1/kreskio.js" data-key="pk_…" async></script>

Paste it into the <head> section of every page, as high as possible – then reports also include errors from the page load itself. The widget loads asynchronously and does not slow the page down. The code also works before the closing </body> tag, just without the errors from before it loads.

• WordPress: use a plugin for adding code to the header (e.g. “WPCode”) or add the code to the theme’s header.php file.
• Shopify: in the theme editor, open the theme.liquid file and paste the code right after <head>.
• React, Next.js, Vue: add the <script> tag to the app’s main template or layout.
• Google Tag Manager: create a “Custom HTML” tag with the code and the “All Pages” trigger.

Team and roles

You invite people to the workspace in the “Team” tab by entering their email address and role. The invitation is valid for 7 days. A person without an account signs up first and then clicks the link in the invitation.

Labels describe what someone does in the team, e.g. “Developer”, “Designer” or “Marketing”. You set them in the “Team” tab with the “Labels” button (up to 3 per person). Administrators and the owner set labels for everyone, and a member sets their own. Labels show up when you assign a report, and on the board you can show only the reports assigned to, say, developers.

Reports

Reports land on a board with status columns. You drag them between columns, assign people and comment. Each report contains a screenshot with marks or a screen recording, a description, the page address and technical details: the browser, system, window size, console errors and failed network requests.

• Statuses: New, In progress, In review, Resolved.
• Moving a report to “In review” emails the client asking them to check the fix. The client answers “It works” or “It still does not work” in the portal, and you get a notification; if it still does not work, also an email.
• A client can also do a “Page review”: they click one element after another, add a sentence to each and send them all at once. Each note arrives as a separate report with a screenshot, a frame around the element and a pin on it, so you can assign and close them one by one.
• With a recording, console errors and network requests have a timestamp, e.g. “▶ 0:12”. Clicking it jumps the video to the moment the error happened.
• Cards and the list show a device badge on reports sent from a phone or tablet, and you can filter the board by device. The report details always show the device, including “Computer”.
• A client can mark several places with numbered circles. The description then arrives as a list “1. …, 2. …” with the same numbers as the circles on the screenshot.
• A report pinned to an element shows which element of the page it is about (“Pinned to …”).
• Internal comments (team only) and public ones (visible to the reporter).
• The reporter gets an email with a link to the portal, where they see the status and your public replies.
• The bell in the top bar and the counter next to “Reports” tell you about a new report right away. The owner and administrators get an email about 30 minutes later: reports from that time arrive in one message.
• The client also gets messages in batches: one confirmation when they send several notes in a row, and one update when you resolve several of their reports at once.
• Webhook notifications to Make, Zapier, n8n or Slack. A Jira integration is coming soon.

Besides the board, you have the “List” and “Closed” tabs. On the list you select several reports and change their status, assignee or due date at once; the owner and administrators can also delete them. “Closed” is the archive of reports taken off the board – you bring one back by changing its status. The client does not get an email about closing, and in the portal they see that the team closed the report. You can also assign a person without opening the report by clicking the avatar on the card.

In the report details, the ‹ › arrows next to the number go to the previous and next report in the same section, e.g. in the “New” column, and the outer buttons jump to the first and the last one. The counter next to them shows where you are, e.g. “3 of 12 · New”. The arrows keep the filters and order of the board or list, so with “Assigned to me” turned on you only go through your own reports. When you change the status, “Next” keeps going through the section the report came from – so you can go through all new reports one after another.

Fixing with AI: in the report details, the “Copy for AI” button copies the report as a ready task – the description, page, browser, marked element, console errors and failed requests. Paste it into Claude Code, Cursor or another assistant in the website’s repository. “Download screenshot” saves the screenshot with the client’s marks, which you attach to the task, because the assistant cannot open a private link. A report usually comes from the live version (e.g. sklep.pl), while you make the fix locally (e.g. sklep.test). When you enter the local version address in the project settings, the task gives a ready link, e.g. https://sklep.test/koszyk, and the client’s window size; without it, just the page path, e.g. /koszyk. At the end, the task asks the assistant for a short reply to the client in the client’s language – paste it as a comment “Visible to the reporter” before you move the report to “In review”.

My tasks and due dates

You can give every report a due date, the day by which the team wants it done. In the report details, click the “Due date” field and choose “Today”, “Tomorrow”, “Friday”, “In a week” or any day from the calendar. On the list you can select several reports and set their due date at once.

• On cards and on the list, the due date is red when it has passed and yellow when it is today. Resolved and closed reports are never “overdue”.
• You can sort the list so the nearest due dates are at the top.
• Only the team sees due dates. The client will not see them in the portal or in emails.

The “My tasks” tab in the menu is your list for today. It holds the reports assigned to you that still need work, grouped into: Overdue, Today, This week, Later and No due date. Reports “In review” are kept apart, in the “Waiting for the client” group, because now it is the client’s move. You change the status and due date right in the row, and a resolved report disappears from the list on its own.

Ideas

Clients often send not only bugs but also ideas: “a price filter would be handy”, “this form could have fewer fields”. To keep them apart from fixes, Kreskio collects them separately, in the “Ideas” tab. The team and clients vote on them, and you decide which are worth doing – often as extra paid work.

1. 1

   Turn on ideas in the project

   In the project settings, tick “Take ideas in the widget”. From then on, the client on the website chooses “Bug” or “Idea” at the top of the form. An idea has a screenshot with a mark and the page address, but no console or network logs, because it is not about a fault.

2. 2

   Add ideas from conversations

   Note down an idea from a call or meeting in the “Ideas” tab with the “Add idea” button: choose the project, write the idea and add details if you like.

3. 3

   Vote and comment

   On the list, click the thumb next to an idea to add a vote (+1), and click again to take it back. The most supported ideas are at the top. The idea details show who voted, and you can comment on it just like on a report – including a reply visible to the client.

4. 4

   Decide

   In the idea details, change the status to “Under consideration”, “Accepted” or “Rejected”. When you reject an idea, it is worth adding a short explanation for the client in a comment.

5. 5

   Turn it into a task

   When an idea is going to be done, click “Turn into a task”. It goes to the board as a new report, with the same number, comments and votes, and stays visible among the accepted ideas marked “Task on the board”.

• The “Pending”, “Accepted” and “Rejected” tabs split ideas by status. You can narrow the list to a project and sort it by votes or newest first.
• The bell (“New idea from…”) and the counter next to “Ideas” in the menu tell you about a new idea. Ideas are not included in the batch email about new reports.
• An idea does not have bug statuses, so the client will not get a “Check the fix” email by mistake. Such emails only come after the idea is turned into a task.
• The client sees their ideas in the portal, together with the idea’s status and your replies.
• Ideas are not on the board, in the report counter or on the list AI assistants see. Webhooks have a “type” field with the value “bug” or “idea”, so you can tell an idea from a bug in your own tools.

Revision rounds

When your contract says, for example, “3 revision rounds”, Kreskio keeps track of them for you. Instead of sending notes one by one over several weeks, the client collects them on the website and sends the whole round with one button. You get one notification and work on the full set. Revision rounds are available on the Agency plan and during the trial.

1. 1

   Turn on rounds in the project

   In the project settings, tick “Count revision rounds” and enter the number of rounds (from 1 to 10). A “Revision rounds” card appears on the project page.

2. 2

   The client collects notes

   After clicking the report button, the client sees “Round 1 of 3” and the number of notes collected. On the board these notes are greyed out and tagged “Round 1 · collecting”. You get no notifications, emails or webhooks about them until the client sends the round.

3. 3

   The client sends the round

   With the “Send round 1 to the agency” button. The team gets one notification in the bell, and the owner and administrators get one email with the list of notes. Webhooks receive each note separately, and the client gets an email confirming the whole round.

4. 4

   You fix the notes and mark the round

   On the project page, click “Round fixed” next to the sent round. The client gets an email asking them to check the website and from then on can send the next round. They can start collecting notes for it even earlier.

5. 5

   The client accepts the round

   In the portal, the client clicks “Accept the round” next to the fixed round. You get a notification, and the round shows “Accepted by…” with the date. If a note still does not work, the client writes about it on that note or adds it to the next round.

• Notes sent after the last agreed round reach you right away, tagged “out of rounds”. It is a good moment to talk about extra paid work.
• Team reports (from the extension, from the widget in team mode and from the app) and client ideas do not count towards rounds.
• The client sees their rounds in the portal: which are fixed, which one is with you, which one they are collecting and how many are left.
• Every sent round has a PDF acceptance record – the “PDF” button next to the round on the project page. It contains the dates of sending and fixing, the list of notes with screenshots, and who accepted the round and when. The client downloads the same record in the portal.
• When the client has collected notes for a round and adds nothing and does not send it for 3 days, they get a reminder email with a button to the website. The reminder comes once; it comes again only when the client adds more notes and leaves the round again. It does not come while you are fixing the previous round.
• When you turn rounds off, the notes from an unsent round reach you as regular reports.

AI assistants: Claude Code and Cursor

Instead of copying a report with the “Copy for AI” button, you can let the assistant fetch it by itself. Claude Code, Cursor and other assistants that support MCP servers then read a report by its link or number: the description, page, browser, marked element, console errors, failed requests and the client’s screenshot as an image.

1. 1

   Create a key

   Settings → AI assistants. Name the key, e.g. “Claude Code – laptop”, and click “Create key”. Kreskio shows it only once, together with ready-made commands.

2. 2

   Connect the assistant

   Claude Code: copy the command from the “Claude Code” tab and run it once in the terminal. Kreskio will be available in every repository, also in the Code tab of the Claude app. Cursor: copy the settings from the “Cursor” tab and paste them in Settings → MCP → “Add new MCP server” (the mcp.json file).

3. 3

   Point to the project in the repository (recommended)

   On the project page in Kreskio, in the “For your team” card → “AI assistants”, copy the ready-made note and paste it into the CLAUDE.md file in the root folder of the website’s repository (in Cursor: AGENTS.md). The assistant will then know which reports belong to this code and will not guess by addresses.

4. 4

   Ask for a fix

   In the website’s repository, write e.g. “Fetch the report https://kreskio.pl/w/agencja/issues/123 from Kreskio and fix the bug” or “report #42 from the Shop project”.

• “Which Kreskio reports are waiting in this project?” – the assistant matches the repository to the project by the website address and shows the list.
• “Show my urgent Kreskio reports” – only those assigned to you, with the chosen priority.
• “Take the oldest new report from Shop and fix it” – the assistant picks it from the list and fetches the details together with the screenshot and comments.
• “I’ll take it” – with a key that allows changes, the assistant assigns the report to you and sets it to “In progress”.
• “Set the due date of #14 to Friday” – the assistant saves the due date, visible only to the team.
• “The fix is live, reply to the client and move it to review” – the assistant shows you the reply, and once you approve, adds it and sets “In review”.

The code the assistant fixes is always the repository you open the session in: the folder where you run “claude” in the terminal, or the folder chosen in the Claude app or in Cursor. Kreskio only says what is broken. That is why you should open the session in the repository of the website the report is about. The local version address from the project settings does not point to the code: it tells the assistant where to reproduce the bug and check the fix, e.g. https://sklep.test/koszyk instead of the client’s website.

The command for Claude Code looks like this (replace YOUR_KEY with your key):

claude mcp add --transport http --scope user kreskio https://kreskio.pl/mcp --header "Authorization: Bearer YOUR_KEY"

And the settings for Cursor like this:

{
  "mcpServers": {
    "kreskio": {
      "url": "https://kreskio.pl/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_KEY"
      }
    }
  }
}

• A regular key only reads reports. When you tick “Also allow changes” while creating it, the assistant can also add a comment, change the status and priority, set a due date and assign the report to you – in workspaces on the Agency plan and during the trial. It cannot delete anything.
• Changes made by the assistant are saved as yours, and its comments are tagged “via AI assistant”. Before a reply to the client and before “In review”, both of which email the client, the assistant asks for your approval.
• It sees the same reports as you, only from the workspaces you belong to.
• It is valid for 90 days. You can delete it at any time in Settings → AI assistants, e.g. when you lose your laptop.
• When you enter the local version address in the project settings, the assistant gets a link to the reported page on your copy, e.g. https://sklep.test/koszyk.

An example conversation in the website’s repository, with a key that allows changes. Above the replies you can see which Kreskio tool the assistant used – you do not need to know or type them, just write in plain language:

1. You

   Which Kreskio reports are waiting in this project?

2. Claudelist-issues

   3 reports are waiting in the Shop project: #14 · New · priority: high – “Button covers the price” #13 · New – “Search does not work” #11 · In review – “Typo in the footer”

3. You

   Show #14.

4. Claudeget-issue

   The client reported on /koszyk, on an iPhone in a 390 × 844 window, that the “Checkout” button covers the price – they marked the button on the screenshot. No console errors. I will reproduce it on https://sklep.test/koszyk.

5. You

   I’ll take it, fix it.

6. Claudeupdate-issue

   I assigned #14 to you and set it to “In progress”. Cause: the bar with the button has position: fixed with no spacing at the bottom of the page. I fixed resources/css/cart.css. Check https://sklep.test/koszyk in a 390 × 844 window.

7. You

   It works. Note the cause in the report.

8. Claudeadd-comment

   I added an internal comment with the cause and the changed file. Only the team can see it.

9. You

   The fix is live now. Reply to the client and move it to review.

10. Claude

    Here is my suggested reply to the client: “The ‘Checkout’ button no longer covers the price on your phone. Please check it in the cart.” Shall I send it and set “In review”? The client will get an email.

11. You

    Yes.

12. Claudeadd-commentupdate-issue

    Done. The client will see the reply in the portal and in a few minutes will get an email asking them to check the fix.

How to disconnect an assistant from Kreskio:

1. 1

   Delete the key in Kreskio – this cuts off access right away

   Settings → AI assistants → “Delete” next to the key. Every later request with this key will be rejected, no matter on how many computers and in which tools it is saved. Do it right away if the key leaks or you lose your computer.

2. 2

   Remove the server from the assistant

   In Claude Code, run the command below; in Cursor, remove the “kreskio” entry from the mcp.json file. This step alone is not enough: the key would keep working if someone had a copy of it.

claude mcp remove kreskio --scope user

• For a while, without removing it: in Claude Code, type /mcp, choose “kreskio” and turn it off.
• Changing permissions, e.g. from read-only to read and change: create a new key, swap it in the assistant (first “claude mcp remove”, then “claude mcp add”) and delete the old one in Kreskio.

Client portal

The portal is where your client follows their reports and talks to you, without creating an account. No more emails asking “so what about that bug?”.

1. 1

   The client sends a report through the widget

   They enter their name and email. No password, no account.

2. 2

   They get an email with a “Follow the report” button

   The link signs them in to the portal and is valid for 7 days. After that, the client enters their email on the portal page and gets a new link.

3. 3

   In the portal they see the status and your replies

   Progress: New → In progress → In review → Resolved. They also see their screenshot or recording, and only the comments marked “Visible to the reporter”; internal notes and the team’s due dates stay hidden.

4. 4

   You reply to each other

   When you add a public comment, the client gets an email. When the client replies in the portal, the email goes to the person assigned to the report, or to the owner and admins.

5. 5

   The client confirms the fix

   When you move a report to “In review”, the client gets an email asking them to check it. In the portal they click “It works” – the report moves to “Resolved” – or “It still does not work” and describe what is wrong – the report goes back to “In progress” and the assignee gets an email.

6. 6

   Or hears about the fix

   When you move a report straight to “Resolved”, the client gets an email saying the bug has been fixed.

Webhooks

A webhook is an address that Kreskio automatically sends a message to when something happens: a new report comes in, a status changes or someone adds a comment. That way reports land where your team already works.

• Slack or Teams: a new report shows up as a message in a channel, e.g. #bugs.
• Google Sheets: each report is added as a row, e.g. to an overview you share with the client.
• Trello, Asana, ClickUp or your CRM: a report creates a new task.

1. 1

   Create a scenario in Make, Zapier or n8n

   Choose the “Webhook” trigger (in Make: “Custom webhook”, in Zapier: “Catch Hook”). The tool gives you an address starting with https://.

2. 2

   Paste that address below and pick the events

   For example, only “New report” if you want Slack notifications about new bugs.

3. 3

   Click “Send test”

   Kreskio sends a sample message and Make or Zapier picks up its fields: title, description, status, page address, reporter and the link to the report.

4. 4

   Finish the scenario

   Add an action, e.g. “Send a Slack message”, and use the report’s fields in it.

Every message is signed with the secret shown next to the webhook (the Kreskio-Signature header), so your system can check that it really comes from Kreskio. If the address is temporarily not responding, Kreskio retries several times over 2 hours. You can see the history of recent deliveries next to each webhook.

You set up webhooks on the project page, in the “Webhooks” section. The workspace owner and administrators can see it.

Team mode in the widget

Team mode lets you and your team use the widget on the client’s website as the team rather than as an anonymous reporter. There is no Chrome extension to install, so it works in any browser, phones included.

1. 1

   Click “Report a bug”, then “Team sign-in”

   The link is at the bottom of the window where you choose a screenshot or a recording; on a phone, at the bottom of the report form. A small Kreskio window opens; if you are not signed in, sign in with your account. If the browser blocks the window, allow pop-ups for this website.

2. 2

   Click “Turn on team mode”

   The window closes by itself and a “Team mode” bar with your name appears on the page.

3. 3

   Turn on pins

   The “Show pins” button draws numbered markers next to the elements that open reports are about. Click a marker to read the report and jump to it in Kreskio.

4. 4

   Report as a team member

   Reports sent in team mode go out as you straight away, without entering a name and email. Screenshots, recordings and “Point at element” all work.

5. 5

   Click “Sign out” when you are done

   Especially on someone else’s computer, e.g. at the client’s office. Access expires by itself anyway after 8 hours or when you close the tab.

• Team mode only works on websites with the Kreskio widget and only for team members of this workspace.
• Access covers only this one project and expires after 8 hours.
• The client only sees a small “Team sign-in” link; without an account on your team it gives them nothing.

Chrome extension

The extension lets your team report bugs on any website, also one without the Kreskio code, e.g. the client’s live website. Clients do not need it: they report with the button on the website. You will find the package to download in the Guide, in the “Chrome extension” section.

The extension is in the Chrome Web Store. It works in Google Chrome and in Microsoft Edge, which installs it from the same store. It is not available for Firefox and Safari yet: there, report bugs with the Kreskio button on the website.

1. 1

   Open Kreskio in the Chrome Web Store

   Click “Add to Chrome” above or go to https://chromewebstore.google.com/detail/kreskio-%E2%80%93-zg%C5%82aszanie-b%C5%82%C4%99d/oheolljbnkokeakobfehiahdigdmedpm.

2. 2

   Add the extension

   On the store page, click “Add to Chrome”, then “Add extension”.

3. 3

   Pin the icon to the toolbar

   Click the puzzle icon next to the address bar, then the pin next to Kreskio. The icon will always be at hand.

4. 4

   Connect your account

   Click the Kreskio icon, then “Connect your account”. A Kreskio tab opens where you confirm the connection. Done.

In Microsoft Edge the steps are the same, with two differences:

• Adding: At the top of the store page, click “Allow extensions from other stores” and confirm, then click “Get” and “Add extension”.
• Pinning the icon: Click the puzzle icon next to the address bar, then the eye icon next to Kreskio (“Show in toolbar”). The icon will always be at hand.

If the store is blocked, e.g. by a company computer policy, you can also install the extension from a zip package – the steps are in the app under “Chrome extension”.

• A screenshot of the visible part of the page in one click, with passwords and card details masked.
• The project is picked automatically by the website’s domain.
• “Point at element” pins the report to a specific button, image or paragraph.
• “Show pins on this page” draws numbered markers next to elements with open reports. Clicking a marker shows the title, status and a link to the report. Reports whose element is no longer on the page go to the “Detached” list.
• “Record this tab” records the current tab together with the page sound and your voice (up to 5 minutes), without a screen picker. The first time, the extension asks once for access to the microphone.
• From version 0.4.2, the same tools as in the widget: frames (default), numbered circles with a description for each, arrows, highlighter, text, blur, colour and line width choice, and removing marks.
• From version 0.4.3, the “Page review” button in the extension window: you click one element of the page after another, add a note to each and send them all at once. Each note arrives as a separate report with a screenshot of the tab, a frame around the element and a pin. It works on any website, also without the widget.
• The extension version is shown at the bottom of its window. When a newer one is available in Kreskio, the window tells you and leads you to the download.

Plan, payments and limits

A new workspace starts with a trial on the Agency plan, so everything works in it. After that, you order a plan in the “Billing” tab and pay by bank transfer, and the bill arrives by email. After the paid period ends, you still see your reports, but the widget and the extension no longer accept new ones.

• Current prices and limits of both plans are in the “Billing” tab and on the home page.
• You change your plan by ordering another one in “Billing”. Once it is paid, the workspace switches to the new plan right away, and the days left on the previous plan turn into days of the new plan of the same value (based on monthly prices). Example: 30 days of the PLN 59 plan is about 15 days of the PLN 119 plan.
• You can move to a lower plan when the workspace fits within its limits. If you have, for example, more projects or people (including invitations) than Start allows, “Billing” shows what you need to remove before you order Start. File storage does not count here.

• A plan has limits: the number of projects, team members (including pending invitations), websites in one project and storage for screenshots and recordings. You can see your current usage in the “Billing” tab.
• Addresses for local testing (localhost, 127.0.0.1, *.test, *.local) do not count as websites, and example.com, www.example.com and *.example.com count as one.
• Once you reach a limit, you cannot add another project or person. When storage runs out, reports still come in, just without the screenshot and recording – the reporter sees a message about it.
• Nothing already saved is deleted. Need higher limits? Write to us.

Account security

• Change your name, email and password in the user menu (bottom left corner), under “Settings”.
• Turn on two-factor authentication (2FA) in the “Security” tab. Keep the recovery codes in a safe place.
• You can add a passkey to sign in with your fingerprint, face or device PIN.
• In the “Appearance” tab you choose a light, dark or system theme.

Frequently asked questions

I cannot see the “Report a bug” button on the website. What should I do?

Check that the website’s domain is on the project’s list of allowed domains, that the widget is turned on in the project settings and that the code is pasted on that page. If the website uses a cache, clear it.

Why does the email about a new report arrive with a delay?

Kreskio waits about 30 minutes and combines reports from one project into one message, so a client who sends several notes in a row does not flood you with emails. In the app you see the report right away: at the bell and in the “Reports” tab.

How is an idea different from a bug report?

A bug is something that does not work – it goes to the board and moves through the statuses to “Resolved”, and at the end the client checks the fix. An idea is a suggested change – it waits in the “Ideas” tab for votes and your decision, and goes to the board only after you click “Turn into a task”.

Does the client see the due dates of reports?

No. A due date is the team’s internal plan: it is not in the client portal, in emails to the client or in webhooks. The client sees only the status and replies marked as visible to the reporter.

Does the client need an account?

No. The client reports bugs right on the website. Only the people who handle reports need an account.

Does the widget slow the website down?

No. The script is a few kilobytes and loads asynchronously, after the page content has loaded.

I did not get the invitation. What now?

Check your spam folder. A workspace administrator can cancel the invitation and send it again in the “Team” tab.

How do I move a project to another workspace?

That is not possible yet. Create a new project in the target workspace and replace the code on the website.