Product guide
Settings
Users
Admin Users
Users have full access to GlassDollar’s capabilities. They can search for solutions, access the entire company CRM, create open challenges, drive projects through the VCL funnel, and access analytics.
| Setting | What it does |
|---|---|
| Allowed email domains | Defines which domains can be invited as admins or access shared content |
| Admin user table | Lists everyone with admin access — name, team, last login, created date, notifications, role |
| Invite users | Add a user by email, assign access level and team, send the invite link |
| Innovation Lead | Always sees lists/projects, even private ones |
How-to guides — Admin Users
Teams
Teams let you divide your users into named groups that mirror how your innovation program is organized. Please make sure the team function is enabled for your account — this depends on your contract.
Creating a team
- Go to Settings → Teams and click + New team
- Enter a team name and add admin users — users can belong to multiple teams
- Assign the team when creating or editing projects and lists
How-to guides
Organization
| Setting | What it does |
|---|---|
| Platform name | The name displayed as your platform’s title — shown in the Innovation Hub, exports, and stakeholder-facing views |
| Logo | Upload or replace your organization’s logo — appears in the Innovation Hub header and exports |
For changes to SSO/SAML, data residency, subscription details, or allowed email domains, contact your GlassDollar account manager.
How-to guides
Departments
Departments define the organizational structure inside GlassDollar. Every project is assigned to a department — enabling cross-department filtering, BU-level reporting, and stakeholder alignment.
What you can do
| Action | How |
|---|---|
| Add a department | Click + Add department — enter a name, Division/Brand label, and optional description |
| Delete a department | Click the trash icon — deleting does not delete associated projects |
| Edit / rename | Not currently available — contact your account manager to rename or restructure departments |
Department fields
| Field | What it’s for |
|---|---|
| Name | Displayed across projects and analytics |
| Division / Brand | Optional grouping — useful for multi-brand organisations |
| Description | Brief description of who belongs to this department |
How-to guides
Directory
Business Units have limited access to GlassDollar. They can search for solutions, create their own lists, and collaborate on lists and projects shared with them by admin users.
Business Units
| Action | What it does |
|---|---|
| + New BU stakeholder | Add business contacts and keep org data current |
| Inspire Stakeholders | Turn business-unit interest into actionable leads |
| Request form link | Invite stakeholders to submit needs directly |
How-to guides — Business Units
What you can do
| Action | How |
|---|---|
| Add a department | Click + Add department — enter a name, Division/Brand label, and optional description |
| Delete a department | Click the trash icon — deleting does not delete associated projects |
| Edit / rename | Not currently available — contact your account manager to rename or restructure departments |
Innovation Hub
The Innovation Hub is the internal storefront of innovation — a single entry point that explains venture clienting, collects needs and ideas, and showcases startup collaborations.
What you can build
| Page type | What it’s for |
|---|---|
| Shareable landing page | Introduce venture clienting, how the process works, and how to take part |
| ”About” page | Your innovation team’s mission, contacts, process, and success stories |
| Topic / department pages | Dedicated spaces (e.g. “Sustainability Innovations”, “AI in Operations”) |
| “Submit an innovation need” button | Lets any stakeholder describe a challenge → flows in as a structured Need |
Typical use cases
- Launch internal innovation campaigns with a custom URL per department
- Share startup shortlists and announce PoC opportunities
- Collect structured innovation requests from the business
- Brief stakeholders before meetings with relevant lists and projects
Ready to set up your Innovation Hub?
Your customer success manager will guide you through building your first Hub — from the About page to accepting innovation needs from business units.
Contact Customer Success: hannah@glassdollar.com
SourceAI
ℹ️ These settings are currently only editable by your GlassDollar account manager. Contact them to request changes.
Organisation Settings
| Setting | Options | What it controls |
|---|---|---|
| Landscape Categories Limit | Default · Custom (number) | Maximum number of category suggestions in a Landscape search |
| Candidates per search | Default · Custom (number) | How many candidate companies SourceAI evaluates per query |
| Criteria Enrichment Engine | Auto · WebAnswers V2 · WebAnswers V1 | Auto = balanced. V2 = fastest with high accuracy. V1 = most robust, slower. |
Projects
See these settings in context, with screenshots of a live project: Projects page.
Project Types
A project type is a named, end-to-end workflow — the stages a project moves through, the tasks and approvals required at each one, and the terminology used to describe it. Until now, every project ran through the same fixed structure. Now your organization can define how venture clienting actually works across your business units and project managers — tailoring stages, tasks, approvals, and terminology to match how you operate. The playbook that’s powered 1,000+ PoCs on GlassDollar is your starting point: adopt it as-is, or reshape it to fit your process.
This is a step toward decentralized innovation — giving individual teams the freedom to find and test solutions on their own, within the guardrails of an organization-specific playbook. For each project type, you can create tasks specific to that workflow.
| What you can do | Detail |
|---|---|
| Create project types | Define named workflows that match how you work — e.g. “Software Procurement” vs. “Hardware Integration” — so a quick evaluation and a multi-year integration no longer share one rigid path |
| Rename everywhere | Rename phases and section headers (e.g. “PoCs” → “Pilots”, “Assessment” → “Due Diligence”) via Group Labels and Phase Labels below — labels carry through Kanban, scoping, analytics, notes, cards, and lists |
| Define tasks per phase | Define ordered tasks for each phase, each with an owner, approver, due date, docs, and required steps — tasks generate automatically as soon as a project is created |
| Assign owners & approvers | Assign an owner and, where needed, an approver to each task — work then passes through a proper approval gate, and every transition is tracked |
| Attach templates & documents | Attach templates and reference documents directly to a task, so the right resources are available exactly when someone needs to complete it |
| Notify the right people | Notify assignees and approvers automatically on assignments, due dates, and approve/reject decisions — no need to live inside the app |
| Surface tasks on Home | Individual tasks are displayed for the assigned person on their Home screen, across all projects |
Group Labels
A group is one of the broad pipeline stages a project moves through — Ideas, Leads, PoCs, or Implementations — used to organize the Kanban board and navigation.
These labels are visible to everyone in your organization. Any Innovation Lead can update them.
| Default group | Label |
|---|---|
| Ideas | Ideas |
| Leads | Discovery |
| PoCs | PoCs |
| Implementations | Implementations |
Each group keeps its color indicator wherever it appears. Rename a group from this table, or click the revert icon to restore its default name.
Phase Labels
A phase is a more granular step within a group — for example, Sourcing or Assessment within Leads — used to track a project’s progress in detail.
These labels are visible to everyone in your organization. Any Innovation Lead can update them.
| Group | Phases |
|---|---|
| Ideas | Requests, Backlog |
| Leads | Sourcing, Assessment |
| PoCs | PoC Planning, PoC Execution, PoC Success, PoC Fail |
| Implementations | Implementation, Implemented, Scaling, Scaling Completed |
⚠️ Due to backend limitations tied to accurate analytics, it is currently not possible to add or remove groups or phases — only rename them.
Health Status
Automatically surfaces stalling projects. Choose one of three modes:
| Mode | How it works |
|---|---|
| Automatic | Default thresholds apply: 🟢 active in last 10.5 days · 🟡 no change for 10.5 days · 🔴 no change for 14 days |
| Custom | Set your own Amber and Red thresholds in days — same traffic-light logic, your numbers |
| Manual | No automatic calculation — project health is set manually by the project owner at any time |
The health light is calculated automatically unless your organization turns that off (Manual mode). The behavior below applies to both Automatic and Custom — Custom just swaps in your own Amber/Red day counts; the underlying logic is identical.
Organization settings that control it
| Setting | Default | What it does |
|---|---|---|
| Amber threshold | 10.5 days | Days of inactivity before a project can go amber |
| Red threshold | 14 days | Days of inactivity before a project can go red |
| Mode | Automatic | Automatic/Custom vs. manual-only — controls whether the system calculates health at all |
Manual mode
If your organization disables automatic health:
- The light is only ever whatever a person manually sets.
- Time elapsed, task activity, and phase changes never move it — nothing decays automatically.
Automatic & Custom modes
The system picks a color using this priority order:
A) Manual override (temporary) — If someone manually sets green/amber/red, that choice holds, but its clock starts running from the moment it was set: it becomes amber after the amber threshold, then red after the red threshold. A manual green does not stay green forever if nothing else happens — it can still decay. Clearing the override returns the project to automatic calculation.
B) Task activity in the current phase (preferred signal) — If the project has tasks/milestones in its current phase, the system checks the most recent task status change and whether any incomplete task is overdue.
- Overdue incomplete tasks exist → the project cannot be green; recent activity → amber; too long since activity → red.
- No overdue tasks → recent activity (under the amber threshold) → green; medium delay → amber; long delay → red.
C) Fallback: time in current phase — Used only when there’s no useful task-activity signal. Based on how long the project has sat in its current phase: under the amber threshold → green, between amber and red → amber, past the red threshold → red. If phase history is missing, it falls back to the project’s creation date.
When the light changes
| Triggers | |
|---|---|
| Turns/stays green | Project just entered a new phase · a task status was recently updated in the current phase · someone manually set green (until the override ages out) |
| Turns amber | Stuck in the same phase too long with no progress · task activity has gone quiet · overdue tasks exist (and it isn’t already red) · a manual override aged past the amber threshold |
| Turns red | Stuck even longer, past the red threshold · task activity quiet for a long time · overdue tasks + long silence · a manual override aged past the red threshold |
| Resets toward green | Project moves to a new phase (clock restarts) · meaningful task progress in the current phase · someone manually sets green again |
| Does not change | Board filters, views, or sorting change · no real progress and no phase change |
Important nuance: “progress” means staleness, not success
Automatic health asks “has this project shown recent movement in its current phase?” — not “is this project strategically successful?” A project can show green simply because it recently moved phase or had a task updated, even if the underlying work is difficult or its outcome uncertain.
Pain Point AI
Every pain point gets an AI-assisted write-up and a transparent score. The score is not a grade of how well the pain point is written, or how important the topic is — it’s only a check of whether the text answers the guiding questions behind each field. See it filled in on a real project, with a worked example: Projects → Pain Point.
How scoring works
- Each field has a short list of guiding questions, set below.
- After a field is filled in — by AI or by a person — we check whether the text actually answers those questions.
- If it does, that question counts. If the text is empty, vague, or says things like “not specified” / “TBD”, it doesn’t count.
- The field score is just: questions answered ÷ questions asked. So 1 of 2 = 50, 2 of 3 = 67, an empty field = 0.
- The overall score is the average of the fields that are switched on (unscored fields, like Additional Information, are never part of that average).
- Changing a field’s name does nothing to the score. Changing its questions, or editing the text in it, does.
The fields (defaults)
You can rename any of these fields and edit their guiding questions below. Names in this table are the defaults.
| Field | Required to start sourcing? | Guiding questions | Possible scores |
|---|---|---|---|
| Current Challenge | Yes | 1. What’s wrong with the status quo? 2. Why is that happening / what’s causing it? 3. What are the current workflows, KPIs, and constraints? | 0, 33, 67, 100 |
| Expected Outcomes | Yes | 1. What does success look like in measurable KPIs? | 0, 100 |
| Implementation Readiness | No | 1. Is there budget for a PoC or implementation? 2. Is there management / board sponsorship? | 0, 50, 100 |
| Strategic Benefits | No | 1. What strategic advantages would this create? 2. One Business Unit, or company-wide? | 0, 50, 100 |
| Business Impact Potential | No | 1. What measurable outcomes are we talking about (revenue, cost, efficiency, risk, market)? 2. What’s the ROI timeframe? | 0, 50, 100 |
A few things that don’t show up as their own question, but can still appear in the text:
- On Expected Outcomes, a KPI doesn’t have to be a number — time, cost, quality, error rate, and lead time all count.
- On Implementation Readiness, timeframe and decision-maker can show up in the text; they’re not part of the default score.
- On Strategic Benefits, competitive context and “breakthrough vs. incremental” can show up in the text; not part of the default score.
- On Business Impact Potential, a pilot length or a line like “we need this in 6 months” can count as the ROI timeframe answer.
Additional Information is on the form but is never scored. Title, criteria, and known solutions are also AI-filled, and also never scored. Custom fields — up to 5 — work exactly the same way: scored against whatever questions you put on that field.
If you rename or change a field
| Action | Effect |
|---|---|
| Rename only (e.g. Current Challenge → Problem Statement) | The new name shows up on every pain point, including ones already created. The answers stay put. Scoring still uses the same questions. The score doesn’t move. |
| Change the questions | Writing and scoring both follow the new questions. The score updates the next time someone edits that pain point — it isn’t retroactively recalculated for pain points nobody touches. |
| Hide a field | It disappears from the form. Old answers stay in the background and drop out of the score. |
| Toggle Required on/off | Only affects whether you can start sourcing. Current Challenge and Expected Outcomes stay required regardless. |
If someone internally asks “why did the score change?” — it’s because the questions changed or the text changed. Not because the label changed.
API
The GlassDollar API uses Machine-to-Machine (M2M) authentication — designed for service-to-service communication, not browser session tokens. M2M tokens provide secure, programmatic access for automated integrations.
🔑 API keys are not self-generated. Request your API key from your account manager or via the support chat in the platform.
Once you have a key, open Settings → API to explore all available REST endpoints.
Getting started
Step 1 — Get an Access Token
Exchange your API key for an access token:
curl -X POST https://actions-api.glassdollar.com/v1/token \
-H "X-API-Key: YOUR_API_KEY"
The response returns access_token, token_type, and expires_in (seconds until expiry).
Step 2 — Call the API
Pass the access token as a Bearer token in every request:
curl -X GET "https://actions-api.glassdollar.com/v1/projects" \
-H "Authorization: Bearer YOUR_ACCESS_TOKEN"
Key management
| Topic | Detail |
|---|---|
| Where to get keys | Request from your account manager or via the support chat in the platform |
| Key retrieval | The full key is only shown once — store it securely immediately |
| Scope | Each key is tied to a specific organisation and user |
| Token expiry | Access tokens expire after expires_in seconds — request a new token before expiry |