Search K
Appearance
Service Accounts
Service Accounts let you store reusable credentials and settings for external services that MinuteView integrates with. Many features (Mesh, AI assistants, etc.) rely on these accounts, so configuring them correctly is critical.
Creating a Service Account
- Go to Console → Service Accounts.
- Click New.
- Choose a Service Account Type from the list (e.g., AI Model, Microsoft Azure, etc.).
- Enter a Name (make it descriptive so you know where it’s used).
- Provide the required credentials/parameters for that type.
- Click Save.
You can create multiple accounts of the same type. For example, two AI Model accounts using different providers or models.
Example
Name:
General Chat AI- Type: AI Model
- Provider: OpenAI
- Model:
gpt-4o-mini(general conversational use)
Name:
Advanced Reasoning AI- Type: AI Model
- Provider: Anthropic (Claude)
- Model:
claude-opus-4-8(complex analysis)
Use whichever account best matches the context (general Q&A vs. specialised tasks).
Where Service Accounts Are Used
- Mesh (Search): Requires an AI Model account for intelligent query assistance and result processing. (The Elasticsearch search connection itself is configured during Mesh setup, not as a service account.)
- PowerShell Editor Autocomplete/Assistant: Needs an AI Model service account for inline help.
- Automations / Workflows: Nodes or actions that call external APIs often reference a service account rather than raw credentials.
If a MinuteView feature talks to an external system, odds are it needs a Service Account.
Network Requirements — Server Outbound Access
Every service account that talks to a cloud service requires the MinuteView server to have outbound internet access to that provider's host(s) — regardless of how it authenticates. Service accounts run server-side: MinuteView (and, for workflow nodes, the automation engine) makes the calls, not the user's browser. If your organisation restricts outbound traffic from the server, the relevant domains must be whitelisted for HTTPS (port 443) outbound, or the account will fail — often even though credentials are entered correctly.
The difference between account types is only which hosts to whitelist:
OAuth service accounts — the server calls the provider's authentication/token endpoint (for the initial token and automatic background refresh) and the API host:
| Service account type | Domains to whitelist |
|---|---|
| Microsoft Azure / Azure (OAuth) / Business Central / Dynamics 365 | login.microsoftonline.com, graph.microsoft.com (plus api.businesscentral.dynamics.com or your Dynamics 365 org URL for those services) |
| Autodesk | developer.api.autodesk.com, api.userprofile.autodesk.com |
| Google Cloud Platform | oauth2.googleapis.com, www.googleapis.com |
| Bluebeam | api.bluebeam.com (US), api.bluebeamstudio.com.au (AU), api.bluebeamstudio.eu (EU) |
API-key service accounts — no token refresh, but the server still sends the key to the provider's API host:
| Service account type | Domains to whitelist |
|---|---|
| AI Model | Depends on the selected provider: api.openai.com (OpenAI), api.anthropic.com (Anthropic/Claude), or generativelanguage.googleapis.com (Google/Gemini) |
| Monday.com | api.monday.com |
| Zendesk | {your-subdomain}.zendesk.com |
| Odoo | Your Odoo instance URL (Odoo Cloud or on-premises) |
Internal / on-premises account types (Microsoft SQL Server, Autodesk Vault, Bentley ProjectWise) need only network reachability to the relevant server on your own network — no internet access required. (GemBox uses an offline licence key and needs no network access.)
Per-provider detail
Each service account's own setup page (linked in the sidebar) has a Network Requirements section listing the exact domains and what each is used for.
Managing Existing Accounts
- Edit: Select an account to update credentials or parameters.
- Duplicate: Create variants for different use cases (e.g., staging vs production endpoints).
- Delete: Remove unused accounts (ensure nothing references them before deletion).
Best Practices
- Name Clearly: Include purpose and environment (e.g.,
AI-GeneralChat-Prod). - Least Privilege: Only grant the external service permissions needed for the intended use.
- Rotate Secrets: Update keys/tokens regularly and after any suspected compromise.
- Document Usage: Track which workflows/nodes depend on which accounts.
See Also
- Global Settings → Service Account Selection (choosing the AI assistant account)
- Search Connection (Mesh setup requirements)
- Automations & Workflow Nodes (where accounts are referenced)