GNOK BUG HELP CENTER
Good work starts
with a clear next step.
Get your team moving, configure your workspace, and keep human control over AI-assisted changes.
Search topic titles and summaries. All guides are available below without JavaScript.
User guide
Create issues, plan delivery, collaborate and take an AI-assisted fix through human review.
FOR WORKSPACE ADMINISTRATORSAdministrator guide
Connect fields, screens, workflows, access controls and integrations with practical checks.
New to Gnok Bug?
Start with workspace signup and sign-in, then follow your first day. Need a person? Contact support.
Browse the guides
- User guide
Your first day
Get from an approved workspace to an issue your team can act on.
- User guide
Find your work
Focus, project context, search and favorites.
- User guide
Create and update issues
Capture context, assign responsibility and move work forward.
- User guide
Comments, attachments and time
Keep the evidence with the issue.
- User guide
Boards and sprints
Turn a saved view into a delivery plan.
- User guide
Search and saved views
Find the right issues and keep useful queries.
- User guide
Projects, roadmaps and releases
Connect daily issues to larger outcomes.
- User guide
Submit and handle support requests
Customer forms and agent queues serve different roles.
- User guide
Analyze an issue and open a draft PR
A human approves the plan and a human decides what merges.
- User guide
Understand AI credits and workspace keys
Purchases, spending authority and usage are separate.
- User guide
Members and invited guests
Use the right workspace and understand the access boundary.
- User guide
When something does not look right
A short checklist before asking for help.
- Admin guide
Set up a workspace
A safe order for the first project and its configuration.
- Admin guide
Save, reopen and recover configuration
Use Form controls; Advanced JSON is optional.
- Admin guide
Projects and filing defaults
Choose the configuration that a project uses.
- Admin guide
Custom fields, choices and conditions
Design a clear filing form without writing JSON.
- Admin guide
Screens and screen schemes
Decide which fields appear for an operation.
- Admin guide
Workflow drafts and publishing
Change behavior in a reviewed, saved revision.
- Admin guide
Issue types and relationships
Choose what a project tracks and how work connects.
- Admin guide
Components, versions, milestones and priorities
Give issues useful delivery metadata.
- Admin guide
Groups, roles and project permissions
Treat access as several independent layers.
- Admin guide
Members, guests and portal customers
Keep organization access and service enrollment distinct.
- Admin guide
Request types and service queues
Build a customer form and its agent view.
- Admin guide
Business calendars and SLA policies
Make timing rules explicit.
- Admin guide
Notification schemes and delivery
Separate recipient rules from transport.
- Admin guide
Webhooks, inbound mail and collectors
Configure a connection before exposing it.
- Admin guide
Teams, initiatives and project dependencies
Organize responsibility and outcomes.
- Admin guide
Saved searches, boards and sprints
Connect query, visualization and planning.
- Admin guide
Configured flags and planning impediments
Two different concepts with different consumers.
- Admin guide
Connect GitHub for the coding agent
Grant repository access deliberately.
- Admin guide
AI credits and workspace spending controls
Approve a bounded allowance without interrupting every task.
- Admin guide
Bring your own API keys
Use your provider account while paying Gnok only for runtime.
- Admin guide
Assistant feature settings
Do not confuse assistant features with coding-agent spending.
- Admin guide
Audit, project keys and recovery
Review changes before relying on them.
- Admin guide
Validate the result and get help
Use a small, repeatable acceptance check.
No matching topics. Try a shorter phrase or open either guide above.