Accounts and sign-in 0.17.0
- The CRM finds the lead and contact (or an organization's lead and company) made from a Pages page (route by-ref), for a person's card.
- The CRM keeps automation rules: when a lead or a deal is added (from a source, or anywhere) or reaches a stage, a rule adds a task for its owner, due some days later, or a tag. A CRM's owners and admins change its rules; a deleted account's own CRM takes its rules with it.
- The CRM reads a calendar's activities: every kind due within a span of days (fewer than 62), done or not, with their record's name; the reader's own or everyone's.
- The CRM adds people from Pages events a space's managers choose (follows, product follows, asks to test, feedback, replies), from public page details only, from the moment it is switched on (routes capture and capture-choice; capture-choice answers while the CRM is off). Opting out, or deleting the account, removes the unconverted leads it added. Privacy Notice 2026-10-29 (PRIVACY_VERSION) says so.
- The CRM keeps each CRM's own fields on each kind of record (routes fields, field-save and field-delete; 30 a kind, changed by its owners and admins), and each record's values for them. A field taken away takes its values with it; converting a lead carries its values to the fields with the same name and type; a deleted account's own CRM takes its fields with it. A list (route records) sorts by any of them and narrows by one that is a choice or a yes or no (field and value); a report groups by one of those, in the order of its choices.
- The CRM keeps tags, each record's history of changes, and each person's saved views and email templates; its lists filter, sort and count; it searches across every kind, changes many records at once, finds and merges duplicates, and its summary adds the forecast, win rate and what closes this month.
- The CRM's summary adds the months around the reader's: deals won in each, and open deals' amounts and forecast by the month they close. It also names the reader's records that want looking at. Its lists filter by the month a deal closes.
- A product's page can take messages for its makers: with *Messages with the form on its products' pages* switched on in a CRM's Leads from Pages, anyone may write to its makers from its page on the website, signed in or not, once they agree to the makers keeping their message. Each message adds its sender to the CRM as a lead (source Web form), or goes to the lead or contact with that email already, with a task to answer it due that day. 5 messages an hour from one address and 50 a day to one product; a message that fills in a field people never see is kept nowhere.
- The CRM keeps goals for each month, a person's or the whole CRM's: deals won (their amount, or how many) or activities logged, read with how far this month got. A person sets their own; a CRM's owners and admins set anyone's. A deleted account's goals go with it.
- The CRM keeps products: a price book of up to 500 a CRM, each with a code, a price in a currency and perhaps one of its own products on Pages, kept by its owners and admins. A deal carries up to 50 lines, each a product of the price book or one written in, with a quantity, a price and a discount; its amount is their total, kept in its history, and is no longer set by hand. A deleted account's or CRM's products and lines go with it.
- The CRM logs messages read from a person's own mailbox as email activities on the leads and contacts who sent them, once a CRM a message: who sent it, when, its subject and its first words. To find them, the app sends only a four-hex-digit fingerprint of each sender's address, so the service never learns the address of someone who wrote to them unless they are in the CRM. A deleted account's or CRM's logged replies go with it.
- The CRM reports a kind's records, or its activities, grouped by one field and then by another (a deal's stage, owner, company or close month; a lead's status, source or month added), over a period: each group's count and, for deals, amounts and forecast, with the totals.
- The CRM keeps each person's saved reports beside their saved list views and email templates.
- CRM reports group deals by product, and a deal list narrows to the deals carrying a product.
- Task threads in a shared project: each person's Alelyon publishes the names of their task threads there, with whether each is at work, waiting on them, quiet or done, how many sessions it holds and when it last changed (never what a thread or its sessions say), and the others in the project read them (`publish-threads` and `threads` under `/identity/native/projects/`). A person's threads go when they leave the project or are removed, with the project and with the account, and a thread that has not changed for a week is dropped.