Open Source on ZopDay: One Link Adds the Whole Plan
When a project is approved for the open source program, the applicant gets an email with a link. The link opens a page in ZopDay that shows what the plan includes: ZopDay Pro, ZopCloud credit, or both. The applicant chooses the organisation to add it to, or creates a new one, and the page confirms when it is done.
The Claim Page Shows the Plan and Lets the Applicant Choose an Organisation
After a project is approved for the open source program, the applicant receives an email with a link. The link opens a page in ZopDay that shows what the plan includes: ZopDay Pro, ZopCloud credit, or both.
| What the page shows | What the applicant does |
|---|---|
| Plan contents (ZopDay Pro, ZopCloud credit, or both) | Reviews what is included |
| Organisation selector | Picks an existing organisation or creates a new one |
| Expiry date of the link | Claims before the link expires |
| Confirmation | Sees the page confirm when the plan is added |
The applicant chooses the organisation to add the plan to or creates a new one. The page confirms when it is done.
Teams that manage developer seats at the organisation level keep the same controls after the open source plan is added. The plan does not change how the organisation manages access.
ZopCloud Credit Arrives Monthly and Each Month Lasts 30 Days
ZopCloud credit is added once a month. Each month’s credit can be used for 30 days. The credit resets monthly, and each month’s allocation has its own 30-day window.
Teams tracking billing activity for their organisation see the open source credit alongside any other usage.
Each Link Works Once and Shows Its Expiry Date
Each link works once and shows its expiry date. The applicant knows how long they have to claim the plan, and once the plan is claimed, the link cannot be used again.
Teams using role-based access controls to govern their organisation keep the same permission boundaries after the open source plan is active.
