The Listener The Build Guide licence states the terms for reuse. Each file can inherit it, use a different licence or follow an external source's terms. Access controls who can read the material; a licence controls what they may do with it.
Why it matters
A guide can contain your instructions alongside files with separate terms. One licence choice does not necessarily describe every resource. Check the guide and each file so readers can find the terms that apply to the material they want to use.
Bassilisk records and displays those choices. It does not verify ownership, interpret custom terms or decide whether different licences are compatible. Choose terms you have permission to apply.
How it works
The Build Guide licence
The default is All rights reserved. Bassilisk describes this as allowing others to view the project while requiring your permission for reuse, modification and redistribution.
To inspect or change the guide's licence, follow Manage licence from the Build Guide editor to Publishing. The licence control is separate from the individual resource rows.
The licence list includes restricted terms, hardware licences, software licences, Creative Commons licences and custom terms. Read the selected licence's summary and full terms. The registry records commercial use, modifications, redistribution and remix publication, together with conditions such as attribution, preserved notices and source disclosure.
Each file's licence
In the Build Guide editor, open a resource under Files & resources. Its Licence control has these modes:
- Inherit Build Guide licence uses the guide's licence. This is the default for a new resource.
- Use a different licence lets you choose a Resource licence for that file only.
- Licence managed by external source leaves the terms with the external provider. This choice appears for external resources, not uploaded files.
For example, your guide can retain its default terms while a software file uses its own licence. An externally hosted resource can point readers to the provider's terms. Check each resource's licence instead of assuming every file inherits the guide selection.
Custom terms
Choose Custom terms when supplying terms outside the list. Enter a Custom licence name and the complete terms: Full terms for the guide, or Full custom terms for a resource. The name can contain up to 100 characters; the terms can contain up to 10,000. A name alone is not enough.
Custom terms can apply to the guide or to a file with a different licence. Bassilisk displays your text. Readers need to read it to determine permissions; the site does not turn custom wording into an automatic permission decision.
What readers may do
Start with the licence shown for the material. In Bassilisk's registry, Personal use only permits making and modifying a copy for personal use, but not commercial use or redistribution. Other selections have different permissions and conditions. Follow their full terms.
The public guide licence comes from the approved version. Saving a different licence in your working build does not replace the published terms. Submit the changes for review through the build's publication workflow.
What to check
Check the guide selection, every file's mode and any custom text. Before resources can be published, confirm that you own them or have permission to publish them under the selected terms. Changes to the resource list or licensing can require a fresh confirmation.
Check access separately. Being able to read or download a file does not by itself describe reuse permission. A licence selection also does not grant access to restricted material.
Common mistakes
- Assuming every file uses the Build Guide licence without checking its mode.
- Entering only a short custom licence name and leaving the full terms empty.
- Treating access to a download as permission to redistribute it.
- Expecting a saved licence edit to replace the published licence immediately.
Related
Read Showcase and Build Guide for the editor split and Publish your build for submitting changes.