Help Center
Find practical guidance for navigating organizations, setting up roles, collecting member details, and using the main product surfaces without digging through technical documentation.
Help
Help Center
Product help for navigating organizations, managing invites, reviewing members, and understanding the main pages in Keypiece.
Quick start
If you are setting up an organization for the first time, follow this order so access, onboarding, and member data all line up cleanly.
Step 1
Check your programme workspace
If you are in the Venture Programme, begin from your dashboard and team workspace so you can see pending reflections, stage context, meeting notes, and your task board in one flow.
Step 2
Open your organizations
Start from the Organizations area to see every workspace, program, or team you manage.
Step 3
Set roles first
Use Rules and Roles to define who can manage settings, who can build, and who should only view.
Step 4
Capture the right details
Use Invite Form to ask for the information you want before someone joins, then review it from Members.
Step 5
Review members in one place
The Members page shows the roster, role assignment, and the invite-form details you collected.
Venture Programme
This section is for Entrepreneurship Training Programme and Entrepreneurship Clinic users. Use it when you need the practical answer first: what programme you are in, what stage you are at, where reflections go, and what to update before asking your coach for a change.
Pro-Tip for Markers
When reviewing a team, check the Files tab and the Venture Journey Timeline. These are the main proof-of-work surfaces for screenshots, receipts, pitch decks, and other grading evidence.
Stages at a glance
Question
What is the difference between the Training Programme and the Clinic?
The Training Programme is for registered companies already generating cash flow. The Entrepreneurship Clinic is for structured consultations on business challenges, idea validation, and next-step guidance.
Question
How do I advance my team to the next Stage, such as MVP to Growth?
Stages are managed by your assigned Coach or Admin. To request a stage change, update your Project Idea Record with the latest evidence, traction, and team progress, then notify your coach so they can review and move the team forward.
Question
Where do I find the Reflection prompts assigned to me?
Reflection prompts appear on your Student Dashboard under Pending Reflections. After you submit them, they become visible to your Mentor and Coach in the team timeline for follow-up.
Smart forms
Forms in onboarding are conditional. The system changes what it asks based on the programme path you select so students do not have to fill irrelevant fields.
Question
Why did the form fields change after I selected my organization or programme?
Our forms are smart. If you choose Entrepreneurship Training, the system may ask for business details such as UEN or company information. If you choose Entrepreneurship Clinic, it may ask for your business challenge, consultation needs, or validation context instead.
If Training
Expect fields for UEN, bank details, and revenue model so the onboarding matches registered companies with commercial activity.
If Clinic
Expect fields for problem description and consultation slot preference so the clinic team can prepare the right support session.
Privacy and access
The workspace is designed around programme confidentiality. Team records should only be visible to the people directly supporting that team.
Question
Who can see my Meeting Notes and Reflections?
Your records are private. Only you as the student, your assigned Admin Coach, and your specifically assigned Industry Mentor can see your team's workspace. Other students and unrelated staff cannot access your data.
Meeting notes to tasks
Use meeting notes as the source of truth, then push clear action items into execution. This keeps reviews, coaching feedback, and board work connected.
Question
How do I turn a Meeting Action Item into a Task?
Inside a Meeting Note, create the action items with the checklist tool. Then use Sync to Board so each checklist item becomes a card on the Kanban Task Board automatically.
Question
Where should I upload evidence of our progress for review?
Use the Files tab in the channel or workspace area to upload decks, screenshots, financial evidence, and other supporting files. This keeps proof of progress in one place for markers, mentors, and coaches to review.
Quick Tip
When you sync a checklist to the board, the new cards will automatically be labeled [Action Item]. You can find them in the To Do column immediately.
Where to click
Open a Meeting Note, add checklist items, then click Sync to Board to create task cards automatically.
What to upload
Use the Files tab for evidence such as pitch decks, prototypes, screenshots, reports, and progress documents.
Navigating organizations
Each organization page is split into focused sections. Use them by task, not by habit: roles for access, invite form for onboarding questions, members for review, and AI configurations for shared defaults.
Student dashboard
Use this as your home base for pending reflections, team updates, and quick links into the workspace surfaces your coach expects you to keep current.
Overview
Use this page for the high-level picture: boards, invite emails, and the core organization setup.
AI configurations
Set the organization-wide AI routing defaults here when you want a shared starting point for work across the org.
Rules and roles
Manage presets, permissions, and invite links. This is where access is defined before people join.
Invite form
Add the questions people should answer during the join flow, such as school year, company details, or team-specific context.
Members
Review the current roster, see each person’s role, and compare the details collected during onboarding.
Rules and roles
Think of this page as the access control center for an organization. Set up the role presets first, then create invite links from those presets so every person joins with the right permissions from the start.
Create a preset when you need a role beyond the defaults.
Review each permission row to confirm what that role can manage.
Use invite links from the matching preset so the join flow stays aligned with the intended access level.
Invite forms
Invite forms help you collect information before someone becomes a member. Use them for onboarding questions, program screening, or any details that should be stored with the member record.
Add only the questions you actually need.
Use clear labels so the answers make sense later inside Members.
After updating the form, publish it so future invitees see the latest version.
Members
The Members page is your readout after people join. It combines role assignment with the extra details you asked for during the invite flow, so you can review the roster without opening each response separately.
Use the right-side Add details action to go back to Invite Form and add another captured field.
Check the invite-form columns to compare responses across members.
Keep role and onboarding questions separate: roles live in Rules and Roles, answers live in Members.
Boards and docs
Boards are where day-to-day work happens, while docs are useful for notes, playbooks, and shared reference material. Organizations help you group those boards under one shared access model.
Use boards for active execution and coordination.
Use docs for context, instructions, and long-form reference material.
Keep board access aligned with organization roles so collaborators only see what they need.
Common questions
I selected a programme and the onboarding form changed. Is that a bug?
No. The onboarding form is conditional and changes based on the programme or organization flow you selected so you only see fields relevant to your path.
Why am I seeing a 'Permission Denied' or 'Access Restricted' error?
To protect confidentiality, the system restricts access based on your role, such as Student, Mentor, or Coach. You can only edit or view the boards and documents assigned to your specific team. If you think you are seeing this by mistake, contact your Admin Coach.
Who should I contact if I think my team should move to the next venture stage?
Update your Project Idea Record first, then inform your assigned Coach or Admin. They control stage changes after review.
Where can I check reflections, notes, tasks, and evidence without asking staff?
Start with your Student Dashboard for pending reflections, your team timeline for submitted updates, Meeting Notes for action items, your Kanban board for synced tasks, and the Files tab for evidence uploads.
Where should I go first when setting up a new organization?
Start with Rules and Roles, then Invite Form, and only after that begin sharing invite links. That order keeps access and onboarding aligned.
Where do invite-form answers show up later?
They appear in the Members page as additional columns, so you can review the captured details next to each member.
What is the difference between a role and a detail?
A role controls what someone can do. A detail is information you collect about them, such as school year, department, stage, or team context.
When should I change the invite form?
Change it when the organization needs to collect a new data point from future joiners. Existing saved responses remain historical records of what was asked at the time.
Glossary of terms
This glossary is intended for NYP staff, external markers, mentors, and any reviewer who needs a quick definition of programme-specific language used across the workspace.
Admin Coach
The staff member who manages programme oversight, reviews team progress, and controls administrative changes such as venture stage updates.
Cohort
A grouped intake of student teams or ventures moving through the programme during the same cycle.
Entrepreneurship Clinic
A structured consultation flow for teams working through business challenges, validation questions, or strategic issues.
Entrepreneurship Training Programme
The programme track for registered companies already generating cash flow and building venture growth more formally.
Industry Mentor
The assigned mentor supporting a specific team with domain guidance, review, and venture feedback.
Kanban Board
The task board where cards move across columns such as To Do, In Progress, and Done.
Marker
An NYP staff member or external reviewer who checks evidence, progress records, and submitted outputs.
Pending Reflection
A reflection prompt assigned to the student that still needs a response on the dashboard.
Project Idea Record
The main venture record used to keep your current business idea, evidence, traction, and stage request context up to date.
Venture Stage
The maturity level of the team or startup, such as idea, MVP, or growth, managed by the assigned coach or admin.