How to use Giya
Sign in, chat, connect Google / School / Livro, and manage skills.
Giya — How to use the app
Giya is Livro Systems’ assistant for tasks, QA/bugs, and school setup. In Cebuano/Binisaya, giya means to guide, steer, conduct, or give direction. It answers from your account, role, and connected tools—not from access you don’t have.
Open Docs anytime from the home page.
Get started
- Open Giya and choose Sign in.
- Sign in with Livro (or your school ERP, if you opened Giya from a school site).
- Agree to the Terms of Use.
- Finish onboarding (name, role, focus) if this is your first time.
- You land in the workspace. Connect Google, School, or GitHub before you ask Giya to use them.
There is no public sign-up. Your Livro or school ERP login creates the Giya account.
Sign in
Livro (usual path)
- Go to Sign in.
- Enter your Livro email and password.
- Check the Terms box, then Sign in with Livro.
School ERP (when Giya is opened from a school site)
- Confirm the ERP site shown on the form.
- Enter email and password, then Sign in.
- If the school asks for OTP, enter the Verification code and Verify & continue.
Opened from an ERP desk with a live session: Giya signs you in automatically—no password.
If Terms change later, a bar appears: Agree and continue.
Onboarding
Skipped if you already have a role.
- What’s your name? — enter your display name, then Continue.
- What is your role? — pick from the cards (for example Tech, Sales, Dev, QA, PO, PM, Finance). Owner, Admin, and Team leader are not listed here.
- What should I help with most?
- Tasks & priorities — overdue work and what to tackle next
- Bug analysis — errors, logs, and likely causes
- School setup — academic year, enrollment, roles
- General help — anything your permissions allow
- Finish, then Open Giya workspace.
You can Redo onboarding from the done screen if you need to change this.
First-run tutorial
New users (no chats yet) see a First steps card on the workspace: XP, level, and missions.
| Mission | How |
|---|---|
| Ask Giya something | Send your first message |
| Open tools | Layers button, bottom right (if your role has Google / School / Livro / GitHub) |
| Open your profile | Click your name in the sidebar |
| Browse skills | Profile → Skills — install one or add your own |
Later hides the card until the next visit. Skip tutorial dismisses it for good. Completing every mission awards a Guide badge. People who already have chats never see it.
Workspace
This is the main screen.
Left sidebar (use Show sidebar if it is collapsed)
- New chat — start a blank conversation.
- Chats — reopen past conversations.
- Canvas — Web Pages, Web Forms, and Print Formats Giya generated (one canvas per chat).
- Trash icon on a chat → Archive chat.
- Your name and email open Profile.
- Log out ends the session.
- Admins see Control center (users, teams, schools, roles).
Chat
Greeting is Hi, {your first name}. Ask about tasks, bugs, or school setup.
Chat
- Type in Ask Giya (example:
What tasks are overdue?). - Enter sends. Shift+Enter adds a new line.
- Paperclip Upload pictures — images, video, or PDF. Remove a file from the thumbs above the box.
- Ctrl+V pastes images.
- While Giya is answering, use Stop generating.
Canvas — if Giya builds a Web Page, Web Form, Print Format, Script Report, or document, use Show canvas / Hide canvas. Saved canvases also appear under the sidebar Canvas tab.
Chat uses Cursor by default when your role allows it. That is the route that can use ERP, Gmail, and other tools in the same turn. There is no model picker in the composer. Team leaders set Allowed AI models on the team profile.
Which API key is used (personal, team, or system) is set in Profile → Account → Default prompt API key, not in the chat box.
Ask in plain language. Giya matches skills from what you type (for example “file leave” or “morning briefing”). You do not need a / menu.
Connect tools
Bottom-right Open tools (layers button). Tabs depend on your role:
| Tab | For |
|---|---|
| Gmail, Calendar, Meet | |
| School | School ERP site |
| Livro | Livro ERPNext (same login as Giya) |
| GitHub | Repos (only if your role includes GitHub) |
Teachers in a school embed typically see Google only. Close the panel with Dismiss tools.
Theme, Skills, and API settings are in Profile, not this dock.
Google Workspace
- Open tools → Google.
- Connect Google Account and allow Calendar, Meet, and Gmail.
- Use tabs Calendar, Meet, and Gmail.
Calendar — Grid or List. Quick Add → title, date, start, end, optional Meet link → Save Event.
Gmail — Recent Emails. Compose → To, Subject, Message → Send Email.
Meet — Schedule a titled meeting, or Instant Meet. Join opens the call.
If a tab says disabled, open Profile → Tools → APIs, turn on Google Calendar, Google Meet, and/or Gmail API, then Re-Connect if needed.
Ask Giya things like:
- Morning briefing (today’s meetings + unread mail)
- End-of-day wrap-up
- Prep for my next meeting
- Unread mail, urgent mail, draft a decline or follow-up
- Today’s agenda, free slots, conflicts
Connect Google before those requests. For leave email or ERP wrap-up that includes Gmail, keep Gmail enabled.
School ERP
- Open tools → School.
- Enter the School ERP URL (or pick a recent/preset).
- Username / email and password → Connect school.
- Complete OTP if asked.
You should see students, teachers, classes, and Refresh / Logout. Opened from a school desk, the password form may be skipped.
Then ask Giya for enrollment walkthroughs, Print Formats, report cards, grade slips, progress reports, Form 10 / TOR, SF4–SF6, rankings, and related grading reports. Use Cursor (the default) so School ERP tools run.
Livro ERP
Livro is the same session as Sign in with Livro. There is no second password in the tools panel.
Open tools → Livro to see hours, tasks, and sprint backlogs. If it says Livro session missing, Log out and sign in with Livro again.
Ask Giya for customer lookup, invoices, stock, leave (ERP leave + optional email to the approver), overtime, or an end-of-day wrap-up. Connect Google as well if you want the leave email or wrap-up to include Gmail/Calendar.
GitHub
Visible only if your role has GitHub access (often Dev, QA, PO, or admin).
- Open tools → GitHub.
- Paste a personal access token with repo and read:org.
- Save PAT.
- Browse Personal, Collaborator, and Organizations repos. Disconnect removes the token.
Profile
Click your name or email in the left sidebar.
| Tab | What to do |
|---|---|
| Account | Name, email, team, default API key, personal Cursor/Gemini keys |
| Theme | Color presets or a custom theme for this browser |
| Skills | Browse, install, and create skills |
| Tools | Installed MCPs, installed skills, Google APIs, knowledge index |
Account
- View full profile, usage & prompt archives opens your user profile page.
- Edit name, then Save.
- Team — join with a 6-digit code, Leave team (leaders cannot leave), or Manage team if you lead.
- Default prompt API key — Personal key, Team key, or System key, then Save default.
- API keys — add or clear personal Gemini and Cursor keys. Team keys are set by the leader on the team profile.
Theme — presets such as Artisan Teal, or Add a custom theme. Custom themes stay in this browser.
Tools
- MCPs — install or configure extra MCP servers.
- Installed — skills currently active.
- APIs — Google connect and capability toggles.
- Knowledge — files Giya indexed from attachments and output.
Deeper MCP catalogue: /mcp.
Skills
Skills are repeatable workflows. Giya picks them up from normal chat (and from installed marketplace skills).
Create a skill
- Profile → Skills → Add Your Own Skill — name, category, short description, instructions, Private or Published → Save Skill. New skills are private unless you publish them.
Marketplace — search, filter, Install / Uninstall. Delete only skills you authored.
Giya matches installed skills from plain language in chat (the / command menu is not used).
Teams and keys
- Get a 6-digit join code from your team leader.
- Profile → Account → enter the code → Join team.
- Prefer Team key in Default prompt API key when the leader has shared Cursor/Gemini credentials.
Team leaders (from Manage team or Control center):
- Share Cursor and Gemini team keys (Edit keys).
- Set Allowed AI models (Edit models). Cursor should stay allowed if people need ERP + Gmail in one turn.
- See members, join code, and team usage.
Personal keys override team keys when the default is Personal key.
Admin
If you have team-management permission, open Control center in the sidebar.
| Section | What to do |
|---|---|
| Users | Search people, open profiles, change roles |
| Teams | Create team (name, optional description). Share the join code. |
| Schools | Add school (name, URL, school code) for knowledge / school context |
| Roles | Create role and set permissions (GitHub, Google, Livro ERP, School ERP, chat, admin) |
| Feedback | Owners/admins: charts and comments from the Giya AI survey |
Signed-in users can submit the survey from the sidebar Feedback survey (/feedback). Email is stored from the account. You can update your response later.
Back to chat returns to the workspace. Owner and Admin roles are system-protected.
Server Gemini and Google OAuth env vars are documented in GOOGLE_CREDENTIALS.md for DevOps.
Install as an app
On / (or /landing):
- Chrome / Edge — Install app when the browser offers it.
- Android — Chrome ⋮ → Install app or Add to Home screen.
- iPhone — Safari Share → Add to Home Screen.
Standalone windows show Installed. Optional Notifications can be enabled later.
When Giya is embedded in ERP, use Fullscreen / Exit fullscreen.
Tips
- Connect Google and the right ERP tool before asking for mail, leave, wrap-up, or school reports.
- Stay on Cursor (the default) when you need ERP and Gmail in the same request.
- After you Add Your Own Skill, it is available in chat without a reload.
- Use Team keys when your leader has shared credentials.
- If Livro tools fail, sign out and Sign in with Livro again.
Product name: Giya · Maker: Livro Systems Inc.