Skip to main content
Zeno gives outside readers a read-only view of your books, limited to the projects or legal entity you pick. They see the reports, the ledger, and the bills behind the numbers — including the scanned invoices — and nothing outside their scope. There are two ways in, and they show the same thing: Use a link for a one-off — an accountant who needs the year’s numbers. Use a scoped user for someone who’ll come back, like an investor in a project you’re building. From Settings → Books Share Links, click New link.
  1. Label — how you’ll recognize it later, e.g. “Ashbury Residences — Investor Packet”.
  2. Scope — either specific projects and properties, or a whole legal entity. Pick the smallest set that answers their question.
  3. Window — leave both dates blank for a live view that keeps updating. Set them to freeze the view to a period.
  4. Passcode (optional) — a second gate on top of the URL. Send it separately.
  5. Expires on (optional) — the link stops working after this date.
The URL appears once, on creation. Copy it then. Zeno stores only a fingerprint, so a lost link can’t be recovered — revoke it and make a new one.
Anyone holding the URL can open it. Treat it like a password: send it to one person, and revoke it when they’re done.
Revoke stops a link immediately, for everyone holding it. It can’t be undone.

Give someone a scoped login

Better when the reader is a person you’ll deal with again — you’ll know who read the books and when, and there’s no URL to leak or forward. From Settings → Users & Permissions:
  1. Invite them by email with role Member, and under Access preset pick Investor / Outside Viewer. That gives them read-only Books and closes every other module.
  2. Have them sign in once with Google so the account exists.
  3. On their card, next to Books scope, click Limit to specific companies and tick the projects to share. Save.
They now land on their books view at sign-in, and only ever see that. To end it, click Remove next to their scope — or remove them from the organization.
Don’t make a scoped reader an Admin or Manager. Admins are exempt from the scope by design, so an admin with a scope set still sees everything.

What they see

Both routes show the same read-only view, scoped to the projects you chose:
  • Reports — Profit & Loss and P&L Detail, Balance Sheet, Statement of Cash Flows, Trial Balance, A/R and A/P Aging, Open Invoices, Unpaid Bills, Customer and Vendor Balance, Sales by Customer, Expenses by Vendor, Transaction List, Journal. Each exports to PDF, Excel, or CSV.
  • Ledger — the Chart of Accounts with balances, every transaction in scope, and a per-vendor rollup.
  • Detail — click any transaction for the full entry, its lines, and its attachments. Click a bill for the invoice as the vendor sent it — line items, payments applied, and the scan.
They can narrow the dates or, if you scoped them to several projects, switch between them. They can’t reach outside what you set.

What they don’t see

  • Anything outside the scope. Other projects, other entities, and the org-wide dashboard.
  • The rest of Zeno. No Development, Rental, Glass, Contractor, Inbox, Tasks, Documents, or search — so no units, buyers, or draw schedules, even for a project they can see.
  • Your internal record. Vendor and customer pages show the name and their activity in scope, not contact details, notes, tax IDs, or compliance files. Transaction detail shows memos and receipts, not who entered it or the audit trail.
  • Bills that straddle projects. A bill posting to a project they can see and one they can’t is withheld entirely — one scan can’t be redacted down to one project’s lines. Its ledger rows still show; only the bill page and its scan are held back.
Nobody with a share link or a books scope can change anything. Every write is refused.

Read-only staff

Different case: someone on your team who should see the books but never change them. From Settings → Users & Permissions, find them and set their Books tier to Viewer. A Viewer gets the whole Books module in the normal app — every page, every report, the registers — with the buttons that create, edit, pay, or delete gone. It’s org-wide: a Viewer isn’t limited to particular projects. For that, use a books scope.