Funnalized
DEENTell me when it starts
Module 08 · Team & permissions

Everyone sees exactly what they should see — right down to the single field

Roles, four-eyes approvals and a complete audit log — the foundation under every other module.

0Capabilities
0Paths through
0Handovers
0Entries in the catalogue

Screens from a demo workspace. Companies, people and figures are fictitious.

What it does

Team & permissions at work

Five capabilities people actually open Team & permissions for. Everything else it can do is listed in full in section 04 — this is only what stands on its own.

The load-bearing capability

Permissions down to the individual row

Per module and per action — create, read, change, delete — you set the reach: everything, the department, your own reporting line, only your own records, or nothing at all. Five levels for every single operation instead of a crude “admin/user” switch. Each data module gets a branch of its own that you fold open and shut.

Five levels

for every single action, instead of a blunt admin-or-user switch

Approvals and the four-eyes principle

Approval policies attach themselves to critical operations — a role change, a permission change, a quote or contract above the threshold, a bulk export. The operation pauses and only continues once the responsible role confirms. Nobody approves their own request.

Four eyes

nobody approves their own request — the record waits until someone confirms

Access for a limited time only

If somebody briefly needs elevated permissions, they request them with a reason and a duration. A manager approves — no self-approval — the access takes effect immediately and expires by itself when the time is up. A reminder goes out beforehand, so that no permanent right ends up hanging around out of convenience.

Expires

automatically when the period ends — a reminder goes out beforehand

Role simulator — see it before you hand it out

Pick a person, a module, an action — and the app tells you yes or no immediately, plus the reach that actually applies in the end and the reasoning behind it: which rule, which role, which added permission bundle. No guessing whether somebody sees too much or too little; on a “denied” you get a suggestion for how to put it right.

Yes / no

straight away, with scope and reason — and a suggestion when it is a no

Field-level security

Permissions do not stop at the record. Your recruiter sees the salary in the application, the working student next to them only name and status — the same view, two truths. Per role you decide field by field who gets to see what: in sales, recruiting, projects and marketing. In sales the same rule applies to writing as well. And the mask applies to bulk export too — what a role may not see does not even appear as a column in its CSV.

Field by field

who sees what — in sales, recruiting, projects and marketing, and in the CSV too

Interplay

Paths that run through here

Permissions do not hang off a module page, they hang off the record. That is why the same answer holds in every module — there is no second permission system to forget.

Handovers

What Team & permissions receives and passes on

Comes in to Team & permissions
Team & permissions
Goes out of Team & permissions

Team & permissions decides who may see and do what. What a client sees from outside is decided by the customer portal.

Complete

Everything that is in it

0Entries in the catalogue

57 capabilities in 7 groups — complete, not curated.

Honestly

What it does not do

Every limit names the place where it happens instead.

  • Other people’s sessions are off-limits.

    Everyone sees their own signed-in devices and can sign them out. Admins do not get their colleagues’ sessions either — that is deliberate, not a missing view.

  • Funnalized is not an identity provider.

    You do not sign in to other applications with Funnalized — it works the other way round: your team signs in via SSO through your own directory (Microsoft Entra ID, Okta, Google Workspace or any other with OpenID Connect or SAML 2.0), and SCIM creates the accounts and locks them again.

  • Two levels, not arbitrarily many.

    A main workspace with sub-workspaces below it — there is no deeper nesting. A group structure four levels deep is not what this models.

Follow-up

What teams want to know beforehand

Can I see what an employee sees before I give them the role?

Yes. The role simulator shows the interface from their point of view — before you assign it, not after the first complaint.

Can access be time-limited?

Yes, time-boxed and with an expiry. A permission bundle can be layered on top and lapses by itself — nobody has to remember to take it away.

Do our system emails come from our domain?

Partly. The emails around the team — invitation, welcome, role change, deactivation — go out from a mailbox you assign to the template in question; the templates exist and can be edited. Notifications and reminders are sent by our system service: if you choose a sender account, they carry its name, but the address stays ours. Security and mandatory notices always come from our system sender.

Is it logged who changed what?

Yes, and the log cannot be altered afterwards: new entries are added, existing ones stay as they are. Not even an administrator can delete one.

All 57 entries as a list

Permissions, roles and org chart 12

  • Permissions down to the individual row Per module and per action — create, read, change, delete — you set the reach: everything, the department, your own reporting line, only your own records, or nothing at all. Five levels for every single operation instead of a crude “admin/user” switch. Each data module gets a branch of its own that you fold open and shut.
  • Field-level security Permissions do not stop at the record. Your recruiter sees the salary in the application, the working student next to them only name and status — the same view, two truths. Per role you decide field by field who gets to see what: in sales, recruiting, projects and marketing. In sales the same rule applies to writing as well. And the mask applies to bulk export too — what a role may not see does not even appear as a column in its CSV.
  • Role simulator — see it before you hand it out Pick a person, a module, an action — and the app tells you yes or no immediately, plus the reach that actually applies in the end and the reasoning behind it: which rule, which role, which added permission bundle. No guessing whether somebody sees too much or too little; on a “denied” you get a suggestion for how to put it right.
  • Every role in your own colour Every role carries a colour you pick yourself — palette, system colour picker or hex code, the six system roles included. It runs through the whole app: role overview, member list, member profile, departments, role simulator and the profile PDF. You spot who stands for what by the swatch before you have read the name. The colour changes nothing about permissions — the names and rights of the system roles stay locked exactly as they were.
  • Functional roles get a colour of their own too — the same picker, the same hex codes
  • One main manager plus further managers per person — circular reporting (A manages B, B manages A) is not allowed
  • Steers notifications and the “direct reports” permission level
  • The org chart shows only what your own role may see — personal data stays protected
  • Custom fields, with rules behind them Per record type you add fields of your own — text, number, date, or a picklist with options you name yourself. You also decide whether a field must be filled in and whether its value has to be unique; the server checks both, not just the form.
  • Shared team calendars with a role of its own per person — owner, admin, member or viewer
  • Before booking, check whether several people are already committed in that window — across sales appointments and interviews
  • Sidebar, sub-navigation and command search show only what the role has a permission for — no menu item leads into a block

Delegated admins and time-limited access 8

  • Approvals and the four-eyes principle Approval policies attach themselves to critical operations — a role change, a permission change, a quote or contract above the threshold, a bulk export. The operation pauses and only continues once the responsible role confirms. Nobody approves their own request.
  • Permission bundles, time-limited on top A permission bundle lays extra rights on top of a role — with an optional expiry date, without touching the base role. The holiday cover gets exactly what they need and loses it again automatically. A bundle can never take anything away, only add.
  • Access for a limited time only If somebody briefly needs elevated permissions, they request them with a reason and a duration. A manager approves — no self-approval — the access takes effect immediately and expires by itself when the time is up. A reminder goes out beforehand, so that no permanent right ends up hanging around out of convenience.
  • Delegate administration without giving everything away You can delegate team administration to colleagues without opening the whole workspace to them. Who may administer whom is rank-bounded: nobody hands out a role above their own, and nobody throws out a peer.
  • Hand team administration to a role of its own — without opening the whole workspace
  • Just in time: time-limited access on request, with no self-approval
  • Automatic reminder before expiry — no permanent right out of convenience
  • A request for time-limited rights can be denied with a reason, not just approved

Invitations, departments and guests 13

  • Invite with a role — with no permission leak Invite individually or as a bulk import (up to 200 invitations per workspace a day, more on request); the role is already in the invitation. A six-digit code secures the join, and nobody can hand out a role with more permissions than they hold themselves — no manager builds themselves an admin clone.
  • Departments instead of long lists of names Map your structure and give permissions to the department instead of to every individual. The “department” reach in the role levels hangs on exactly that — when the team grows, nobody has to chase twenty checkboxes.
  • Functional roles alongside the main role Some responsibilities do not follow the hierarchy: “AE”, “CSM”, “SDR”. Functional roles are a curated list of labels that sits across the main role — you attach them to records in sales and recruiting and filter by them. They deliberately grant no permissions; that is what permission bundles and approver roles are for.
  • Guests with a narrow view Tax adviser, freelancer, external agency: you invite them as a guest. They become members of your workspace with the role “guest” and sign in through the same sign-in as your team — no second portal, no second password system. Per area you choose read or edit, never delete; plus an expiry date and the channels they write in. They see what they need — and nothing after that.
  • Per guest: areas with read or edit, an expiry date and only the channels you bring them into
  • All guests on one page The guests page shows who has access, to which areas, until when and when they last signed in. There you change the access or revoke it, and open invitations you copy as a link, send again or withdraw.
  • Share documents — quotes, orders, contracts, products — or only invoices, without handing over leads, deals and contacts
  • What is not an option for guests — settings, team, automations, billing or the Academy, for example — is shown greyed out in the dialog, with the reason
  • The invitation carries the logo and colour of your workspace; you see the preview in the dialog already
  • The guest starts on an overview of their own: who invited them, until when the access applies and their areas as links
  • Access revocable at any time — secured by the same permission foundation
  • A guest invitation that got lost or expired you send again
  • New colleagues set themselves up Anyone who accepts an invitation as a newcomer goes through a few short steps: profile picture, name, phone with country code and job title, then light, dark or like the device, an accent colour and the language, and finally, if they like, the email signature. They can change all of it later in the settings.

Security and several workspaces 6

  • Advanced security Two-factor via an authenticator app, mandatory for the whole team if you want it. Plus password policies, an IP allowlist (access only from your own networks), central session management and, per role, even permitted time windows. A complete audit log records every security-relevant step.
  • Sign in with a passkey Instead of a password you sign in with a passkey — Windows Hello, Touch ID or your phone. Fingerprint, face or PIN confirm that it is you, and the device proves that it is yours; a code from the authenticator app is then no longer needed. You name your passkeys in the settings and remove them there again.
  • Confirmation before critical actions Anyone who wants to delete or fully export the workspace, create an API key, change the company login or the security rules, touch payment details or the plan, or give somebody admin rights confirms it once more beforehand — with password, two-factor code or passkey. The confirmation holds for 15 minutes; in everyday work nobody is asked.
  • Release access per member per workspace, never beyond your own account
  • Hand over ownership: a dedicated, extra-secured path, confirmed again with your two-factor code or password
  • Strict rank checking — nobody lifts themselves higher

Audit log, security and activity 5

  • Filter by person, action, period and security event
  • GDPR-aware visibility — other people’s activity only within the permitted frame
  • End sessions centrally, audit-log CSV export for owners and administrators
  • Who changed which role or permission, and when, is recorded without gaps in the permission log
  • All your own signed-in sessions except the current one you end with a single click

Templates for every system email 5

  • Team emails from your own domain Invitation, welcome, role change, deactivation — you edit the texts yourself, and per template you set which of your connected mailboxes it goes out through. So your new colleagues get post from your company, not from a stranger. If a connection fails once, system delivery steps in so that nobody is left without their invitation.
  • Templates for invitation, welcome, role change, (de)activation and removal
  • Placeholders such as name and role are filled in automatically
  • Delivery through your own workspace mailbox
  • Individual templates you can switch off — except the ones without which registration would not work

Roles, sign-in and data export 8

  • Your own roles, not only our six Beyond the roles that ship with the app you create your own — freely named, with a colour and an icon and a permission matrix of their own. If you would rather not start from nothing, duplicate an existing role and change the copy.
  • Admin rights, tightly drawn You give a person exactly the administrative powers they need — members, roles, settings, approvals, invitations — and confine them to one module, one department or one area, with an expiry date if you like. Not all or nothing.
  • Sign in with the account that already exists Anyone with a Google Workspace or Microsoft Entra account signs in with it instead of another password. With company login (SSO) this runs through your own directory — Entra ID, Okta, Google Workspace or any other with OpenID Connect or SAML 2.0 — and can be made mandatory for your domain; SCIM creates the accounts and locks them again. Your workspace’s two-factor requirement still applies.
  • A person’s profile as a PDF — role, department, manager, active permission bundles, security status; the export is logged
  • A JSON export of every member for data portability under Art. 20 GDPR — owner only, and throttled
  • Rules for who may invite whom You decide which roles can be invited at all, which email domains are allowed or blocked, how many invitations one person may have outstanding, and whether an approval is needed before one goes out.
  • A team invitation you send again — with a fresh link and a new expiry
  • A blocked member you unblock again, without having to set them up from scratch
The neighbours

The module before, the module after

All 21 sit in a fixed order — from here it continues in both directions.

Team & permissions is module 8 of 21 — the same order as in the menu and the footer.

One message at launch. After that you'll find me in the top right of the app.

Team & permissions is one of 21. You get all of them.

Sign up and you'll hear from us the moment we go live. Not a newsletter — one message.

€50€150/ month · permanently

Waiting list

Only your email address. No spam, unsubscribe at any time.

See all modules

€50€150/ month · permanently

50 founder placesTell me when it starts