Guides › Administer
Security See which outside applications can reach your workspace and cut one off, review what they saved, and take a copy of the security log. Find it: Settings > Connected Apps. admins only — the page is titled Connected applications Before you start: An administrator role — these pages are not visible to other roles. At least one application authorized by somebody in this workspace. Until then the page is empty, and that is the correct state. See what is connected
Read the list Open Settings → Connected Apps Each row is one authorized application: who allowed it and when, and when it was last used — or never used. Read the badges See the table below. Open It can on any row you are unsure of It lists exactly what the application was granted — see What an app may read. Badge What it means Reviewed by LeadLogiX LeadLogiX has checked who publishes this application. It says nothing about what it may read — that is set separately. Not reviewed Nobody has vouched for it — most applications, including legitimate ones nobody asked us about. Judge it as you would any software you install. Not working Listed but cannot do anything — usually because the person who allowed it was suspended or left. The line underneath says which. Connected is what has access now; Previously Connected is what used to — disconnected applications move there rather than disappearing. Tool Registrations appears only when an application has described its own tools to LeadLogiX; each registration has a Delete button, which stops LeadLogiX reading that tool's calls as evidence on new leads (processed leads keep what it read). A registration still marked Waiting for LeadLogiX review cannot be deleted until it is approved or declined; the application can register it again unless you disconnect it. The search box applies to both application tabs. A connected application, field by field What an app may read
The “It can” list Each row's It can section lists what that application was granted, in plain sentences, folded away by default. What stays on the row is the part a decision turns on: whether it reads customer contact details (highlighted, with a lock icon) and how many permissions it holds. An application that grants nothing is never folded. What appears is what was granted , not what was requested — anything beyond what the approver could give was refused at approval and never appears. What you may see What it means Who can approve Read your leads, their scores and their summaries — without contact details. Scores, qualification and summaries. No names, phone numbers or email addresses. Any role. Read your leads INCLUDING customer names, phone numbers and email addresses. Personal data leaves LeadLogiX. Admin only — an agent or procurement user cannot, even by accident. Read merged customer profiles across your leads. A customer's whole history across every linked conversation — without contact details, and with names removed from written summaries. Needs the Customer Profiles API enabled for your workspace. Any role. Read merged customer profiles INCLUDING customer names, phone numbers and email addresses. The same histories with personal data. Needs the Customer Profiles API enabled. A profile spans conversations across groups, so a user restricted to particular tags can never approve it. Admin only. See which workspace you belong to and your role in it. Membership only — for applications that just sign people in. Any role. Check whether a person your AI is speaking to matches someone already in this workspace. Returns pointers to matching conversations — never their details. The only permission where personal data travels TOWARDS LeadLogiX: the application sends what it holds about the person it is talking to and gets back conversation and profile ids, never contact details. Used to recognise a returning customer mid-call. Needs the Identity Resolution API enabled. Admin only. See which colleagues and which team desks can be contacted, and be given the specific email addresses and phone numbers an admin has cleared for AI use. Contact details nobody has cleared stay hidden. Your own team's contacts, not customers' — including the desk each lead tag routes to. Necessary but not sufficient: every address and number is also gated by its AI agent disclosure box, so an app may hold this and be handed nothing. Never granted by default, even to an app that asks for everything. Admin only. Register tool definitions for this workspace and check their review status. Submitted tools stay inactive until a LeadLogiX administrator approves them. The app can describe its own tools so their calls become evidence. It writes only proposals, and can never approve its own. You can see and remove everything it submitted on the Tool Registrations tab. Needs tool submission enabled. Admin only. Run the automations this workspace has published to applications, and read the results they declare. Each automation is switched on individually by a LeadLogiX administrator; none is available by default. The app can make your workspace ACT — post to a channel, call an outside system, send a message, move a lead into a paid line of business. A published automation returns only the fields it was set up to return, never its logs. Needs automation access enabled. See the Automations tab. Admin only. Read back the notes this application has saved for you in this workspace, and search LeadLogiX's own product documentation. It sees only what it saved itself — not notes from other applications, and not notes belonging to your colleagues. Its own notes, scoped to this workspace, this application and you together — two colleagues may not be entitled to the same leads. The documentation search covers the same public pages for every workspace, read-only. Needs application memory enabled. Any role. Save notes and documents for you in this workspace, and delete them again. Only this application can read what it saves, and only for you. Notes expire on their own; documents saved for search stay until they are deleted or the workspace is. It writes, but only its own notes — nothing in your workspace is disclosed or changed by it. Capped per application per person. Unusual for a writing permission, any role can approve it. Keep assistants that must not read each other's notes as separate applications; a grouping label is for tidiness, not separation. Any role. Read back and list the files this application has saved for you in this workspace. It sees only what it saved itself — not files from other applications, and not files belonging to your colleagues. Files are scoped exactly as notes are. Needs application memory enabled. Any role. Save files for you in this workspace and delete them again. Only this application can read what it saves, and only for you. ⚠ Files do not expire on their own — they stay until they are deleted or the workspace is. Separate from saving notes on purpose: jotting things down is not storing arbitrary files. Discloses and changes nothing else. A cap is the only bound — see the Application storage tab. Any role. Nothing — this authorization no longer grants any access. The permissions behind it have gone, usually after a role change. Listed, but can do nothing. — Disconnect one
Cut an application off Open Settings → Connected Apps Admins only. The page is titled Connected applications . Press Disconnect on the row A confirmation appears — Disconnect <name>? — with Disconnect and Keep it connected . Confirm It can no longer read this workspace's leads, immediately. The row moves to Previously connected, with the date. Disconnecting affects this workspace only — and does not delete what it saved Anything built on the connection stops working until someone authorizes it again. It does not remove the application from LeadLogiX or other workspaces, does not stop someone here authorizing it again tomorrow (tell your team if that is the concern), and does not delete its notes and files — see Application storage. Application storage
What an application has kept, and removing it Open Settings → Application Storage One row per application per person. Search by application, person or collection name; filter by store. Read the three allowances Notes , Searchable and Files — capped separately, never added together (notes and collections in characters, files in bytes). Delete what should not be there A confirmation names what is about to go. Everything that application holds for that person — notes, collections and files — is removed. There is no undo The application simply finds its data absent. Notes expire on their own; collections and files do not — only a delete removes them, so a full allowance is why an application suddenly cannot save anything. A row labelled No longer connected names an application that was removed or withdrew its registration after saving something; its data stays listed and deletable here. Reconnecting an application finds its notes and files where it left them. Security log
The security log Who did what, when — and how to take a copy of it. Open Organization → Security Logs Filter by category, severity, person and date range. The list says when it is showing a window rather than the whole log. Export as CSV or JSON The same events either way — CSV for a spreadsheet, JSON for another system. Read the notice at download time: when an export stops at 10,000 events it says so there, because the file cannot carry the warning. One export a minute, shared by both formats Downloading CSV then JSON straight away is refused — they are one export offered two ways. Both buttons dim and count down; take the one you need first and the other a minute later. Recorded: sign-ins, role changes, key generation, connecting or switching a CRM, and each export of the log itself. To reach further back than 10,000 events, narrow the date range and export again. A JSON export's own count describes the file, not the log. When access fails
It connected, and now nothing works Consent succeeding is not the same as access working Application access is off by default for a workspace, and turning it on is a LeadLogiX administrator's action. Until then approving an application succeeds and every call it makes is refused. If a developer says their integration authorizes cleanly and is then refused on every call, email to have application access enabled. What you see What happened Not working The person who allowed it is suspended or has left. Someone still in the workspace must authorize it again. Nothing — this authorization no longer grants any access. Their role changed and the permissions behind the grant are gone. Re-authorize with an account that has the right role. Everything looks right and calls are refused Application access is probably not enabled for the workspace. Ask LeadLogiX. Apps that run automations
Letting a connected application run an automation An app can run one of your automations by name only when all three are true: An admin approved Automation runs for that application It is its own permission on the consent screen. Approving it publishes nothing by itself. LeadLogiX has enabled automation access for your workspace Ask us. Until then the permission can be approved and every call is refused. The automation itself is published to applications One at a time, by us; none by default. An automation switched on for your own schedules is not reachable until published separately. This lets an application make your workspace act An automation built to act can send a message, call another system, or put work aside for days later, on your behalf. The automations published for this today are answer-only: they check whether an address is well-formed, whether a phone number is dialable, and whether two names refer to the same person. Each run appears under Settings → Scheduled Jobs → History labelled Application , with the application's name, beside Scheduled, Event and Follow-up runs. What “Reviewed” means
A badge, not a permission Reviewed by LeadLogiX means we checked who publishes an application. It does not widen what the application may read, and marking one reviewed grants it nothing — vouching for who somebody is and deciding what they may read are different judgements. Not reviewed means nobody asked us to check: a self-registered application is limited to lead data without contact details until a LeadLogiX administrator deliberately widens it.
Abandoned registrations A nightly sweep lists every self-registered application with no activity for 90 days, and removes nothing unless a LeadLogiX administrator has switched removal on. Activity means being used , not being connected — a seasonal integration nobody has called in months counts as inactive, so say so before it lapses. You'll know it worked: Every application someone authorized is listed with who allowed it and when it was last used; a disconnected one moves to Previously connected. If nothing has ever been authorized the page says Nothing is connected — the normal state for a workspace with no outside integration, not an error to fix. Approved, and every call is refused Application access is not enabled for the workspace — see When access fails. A row says Not working The person who allowed it was suspended or left. Someone in the workspace must authorize it again. An application can no longer save anything Its storage allowance is full — collections and files never expire. Delete under Application storage. The log export was refused An export in either format was taken less than a minute ago. Wait for the countdown.