# How to use Fossa CRM, from sign-in to the API > A client manual for Fossa CRM: sign-in, modules, fields, records, files, dashboard cards, history, API keys, and templates. What each part does, and how you use it. - Canonical HTML: https://fossasoft.com/blog/how-to-use-fossa-crm/ - Markdown: https://fossasoft.com/llms/en/blog/how-to-use-fossa-crm.md - Language: en-GB Fossasoft, Ioannou Metaxa 34, Leptokarya 60063, Greece. Phone +30 2352 031 337. Email info@fossasoft.com. Monday–Friday 09:00–21:00. VAT EL164317738. GEMI 165469048000. Map: https://g.co/kgs/6Lt2hQB This is the operating manual for Fossa CRM , the crm Fossasoft hosts for a client group. It is not a Salesforce pitch, and it is not the same page as CRM setup , which is the service for third-party tools. If you already have a login, this article is for the people who will click around after we open the group. Fossa CRM starts empty on purpose. There is no canned sales pipeline. You add modules, fields, and dashboard cards so the sidebar matches the work. Fossasoft does not offer a public self-serve signup. We create the group, the first users, and the first structure. After that, this page is what a new colleague can read without a call. A group is your company space. Everyone in that group shares modules, records, files, history, dashboard cards, and API keys. Sign-in asks for the group name, then email and password. The panel is available in Greek and English. You switch language from the signed-in menu or on the login screens. The product page lists every function in short form. This article is the same list, with the clicks. If a sentence here disagrees with a button in the panel, the panel is the source of truth and you should tell us so we can fix the copy. Open the login page Fossasoft gave you. Enter group , email , and password , then complete the captcha. After a correct password the app emails a one-time code. Type that code to finish. You can resend a code, but the panel will make you wait between requests, and too many wrong codes send you back to sign-in. A module is a sidebar item: Customers, Jobs, Devices, whatever the group actually keeps. Open Settings → Modules (Manage). Each module gets a UUID when you create it. You set a name, an optional slug, an optional icon picked from the group’s files, and whether it appears in the sidebar. Hidden modules still exist. They just stay off the menu. You can show extra table columns for UUID, created, and updated. Deleting a module deletes its fields and records. That cannot be undone. You can also select several modules and bulk-delete them. Search the module list live, by name, slug, UUID, or date, without reloading the page. Open a module, then its fields. The key is generated from the label. You can move a field up or down. Mark it required, on the form, on the table, or any mix. Removing a field hides it. Values already stored for that key stay in the database but no longer show. Advanced options, depending on type: placeholder, help text, default, min, max, max length, colour, and which module a link points at. These are the field types in the builder. The names match the panel. Click a module in the sidebar. You get a table of rows. New opens the form. Save, edit, or delete one row from its page. Search is live: name, UUID, dates, and the fields you put on the table. Choose how many rows per page. Empty modules say nothing is here yet, not an error. Select rows and use Delete selected for a bulk delete. That cannot be undone. Confirm the count before you accept. The same bulk pattern exists on modules and on API keys. A Link field on Jobs can point at a Customer. On the customer record, Linked from lists incoming pointers: which record, which module, which field. That list searches live and loads ten rows at a time. If a job disappears from a customer page, someone removed the link or deleted the job. History will show which. Open Files . This is a shared drive for the group: folders, upload, rename, preview, replace, delete. Drag files onto the pane or choose them from the computer. They are stored as-is. If a name already exists, the panel asks whether to replace or skip. Some extensions are blocked. When the group is out of space, uploads fail until Fossasoft raises the quota. Images from here can be module icons, sidebar icons, or attachments on a Files field. Deleting a folder deletes what is inside it. That cannot be undone. Preview is for looking, not for editing the file in the browser. Home starts empty. Pin cards on Home, Files, History, Settings, the modules list, or a module page. Maximum twelve cards on one page. Types: a number card, latest rows, or a bar, pie, or line chart. History is every create, update, and delete in the group, with previous and new values, plus sign-in and sign-out. Filter by all, records, modules, files, account, cards, or a single module. Search who, item, action, and date. Actions you will see: created, updated, deleted, signed in, signed out. Empty fields show as empty, not as a guess. Settings holds the account, modules, API docs, and templates. Under the profile you change password with the current password plus a new one, again at least 8 characters. Sidebar icons are optional. Leave them empty, or pick images from the group’s files for Home, Files, History, Manage, and each module. Open Settings → API Docs . Create a named key. The UUID of that key is the secret. Send it as X-Api-Key or as Authorization: Bearer . There is a limit on how many keys a group can hold. Last-used timestamps show whether a key is actually called. Removing a key rejects future requests. Data in the crm stays. The explorer on the same page can run the live endpoints while you are signed in, or with a chosen key: modules, fields, records, incoming links, bulk delete, files (list, mkdir, rename, delete, upload, preview), history, widgets, and template export/import. Search the endpoint list. Fill path, query, and JSON body, then send. Name a key after the system that will use it: a website, a script, another app. There is no built-in Zapier product inside Fossa CRM. If another tool must talk to the same records, it uses this API. Settings → Templates exports the current setup as JSON, or imports a file. Import replaces modules, fields, records, dashboard cards, and history. Users, files, and API keys stay. The panel asks you to tick a warning and type ERASE . That word is the confirm. If you are not sure, export first and stop. A ready template ships with the product: Electronics repair & IT services (Greek: Επισκευές ηλεκτρονικών και υπηρεσίες IT). It is optional. It loads modules, sample records, dashboard cards, and one sample photo into the file manager. You can start blank instead. Labels can be applied in Greek or English when the template supports both. If you are writing or editing the file itself, use how to write a Fossa CRM template JSON : root keys, field types in the file, @module.ref links, dashboard cards, and a minimal example. The easiest path is to paste the markdown spec into an AI with a few sentences about the business and import the JSON it returns. If a button is missing, you are probably on a hidden module or a field that is off the form. If an upload fails, check quota and file type. If an API call returns 401, the key was removed or never sent. If import wiped the wrong group, that cannot be undone from the panel. Call Fossasoft before you type ERASE on a live group. Office hours are Monday–Friday, 09:00–21:00, at Ioannou Metaxa 34, Leptokarya 60063. Email info@fossasoft.com or call +30 2352 031 337 . The product page is Fossa CRM . The short list of functions lives there. This article is the how-to. ## FAQ **Is Fossa CRM the same as the CRM service on this site?** No. The CRM service page is Fossasoft setting up a third-party crm you already chose. Fossa CRM is the product we host. This article is only for Fossa CRM. **Can we create a group ourselves?** No. There is no public signup. Fossasoft opens the group, creates the first users, and agrees the first modules with you. **Does importing a template delete our data?** It deletes modules, fields, records, dashboard cards, and history. Users, files, and API keys stay. You must type ERASE. Export first if the current setup matters. **Where do files live, and who can see them?** In the group file manager. Everyone in the group shares that drive. Quota is set on the group. Field attachments and module icons are picked from the same files. **How does the API authenticate?** Create a key in API Docs. Send the UUID as X-Api-Key or as a Bearer token. You can also try endpoints from the explorer while signed in, without a key. **Where is the JSON format for a template we write ourselves?** In the article how to write a Fossa CRM template JSON. There is also a markdown spec you paste into an AI so it can write the file for you. Export from the panel if you can. The file must have fossacrm_template set to 1. ## Contact - https://fossasoft.com/contact/ - info@fossasoft.com - +30 2352 031 337 - https://fossasoft.com/company/