Understanding how Fields work
There are three different concepts that control Fields:
Permissions determine who can create and share Fields.
Licenses determine who can manually generate Fields.
AI credits determine whether Fields can run automatically.
Although these concepts work together, they're completely independent.
Permissions: who can create Fields?
Creating and sharing Fields is controlled by your workspace's Security settings.
Depending on how your Workspace Admin has configured these settings, Fields can either be managed by Admins only or by all workspace members.
Go to Settings → Security → Fields & Views.
These permissions only affect who can create, edit, and share Fields. They do not determine who can generate them.
Setting | When enabled |
Only admins can create Fields | Only Workspace Admins can create and edit Fields. |
Only admins can share Fields & Meeting Views | Only Workspace Admins can share Fields and Meeting Views. |
If these options are disabled, any workspace member can perform these actions.
💡 Permissions only affect creating and sharing Fields. They do not control who can generate them. |
Licenses: who can generate Fields?
Generating an Field manually depends entirely on the user's license.
License | Can manually generate Fields? |
Basic | ❌ |
Pro | ✅ (if at least one business licence is on the workspace) |
Business | ✅ |
Even if your workspace still has plenty of AI credits available, a Basic user cannot manually generate an Field.
AI credits: how do they work?
AI credits are shared across your entire workspace.
Each paid license contributes AI credits to a common pool.
License | Adds AI credits to the workspace? |
Basic | ❌ |
Pro | ✅ (500 per licence) |
Business | ✅ (1000 per licence) |
These shared credits are used whenever AI runs automatically.
Manual vs automatic AI generation
Manual generation
When you click Generate, Claap checks your license.
If you have a Pro or Business license, the Field is generated.
If you have a Basic license, manual generation isn't available, even if your workspace still has AI credits.
Automatic generation
Auto-run Fields work differently.
When an Field is configured to run automatically, Claap uses the workspace's shared AI credits instead of checking the recording owner's license.
This means that recordings owned by users with a Basic license can still be processed automatically, as long as the workspace has AI credits available.
Example
Imagine your workspace has:
10 Pro users
5 Basic users
A Basic user records a meeting that enters a Meeting View configured with Auto-run Fields.
What happens? | Result |
Fields are generated automatically | ✅ |
AI credits are deducted from the workspace | ✅ |
The Basic user can manually regenerate the Field | ❌ |
Even though the recording belongs to a Basic user, automatic AI generation still works because it uses the shared workspace AI credit pool.
Quick reference
Action | What controls it? |
Create an Field | Workspace permissions |
Share an Field | Workspace permissions |
Generate an Field manually | User license |
Auto-run Fields | Workspace AI credits |
Available AI credits | Number of paid licenses |
FAQ
Why can't a Basic user generate Fields if there are still AI credits available?
Because manual generation depends on the user's license, not on the number of AI credits remaining.
Can recordings owned by Basic users receive Fields?
Yes. If the Field is configured with Auto-run, it will run automatically using the workspace's shared AI credits.
Can an Admin with a Basic license generate Fields?
No. Being an Admin allows them to create and manage Fields (depending on your security settings), but manual generation still requires a Pro or Business license.