Skip to main content
The Action center gathers everything in your workspace that needs a decision from an admin or owner:
  • requests waiting for approval, to publish an app or to enable Lovable backend services,
  • connectors that workspace editors asked for,
  • public apps whose owner left the workspace,
  • projects whose credit usage rose sharply,
  • public apps with critical security findings, and
  • public apps nobody has edited for months.
Lovable ranks the items by priority, so you work through them in one place instead of across settings pages. Approval requests come from workspace policies, and approving one carries the action out. Findings are the problems Lovable flags on projects in its daily check of the workspace. The actions on them transfer ownership, unpublish apps, or ignore security findings.
This page is about the Action center, where you approve or deny requests and act on findings. Looking for every project and its risk? See Security insights. Looking for how much your workspace builds and who uses it? See Insights. The three are different features.
  • Available on: Business and Enterprise plans. Approval requests appear on Enterprise, where workspace policies are available, and so do Abandoned projects findings and Connector requests.
  • Access: Workspace admins and owners
  • Location: Action center in the dashboard sidebar, under Connectors, and from notification links. The mobile app has no entry.

What the Action center shows

The Action center entry in the sidebar shows a badge, so you can see a waiting request from any dashboard page. A number means that many approval requests wait for a decision. An amber dot means at least one finding of Medium or High priority is open. The page has two sections, each with the number of open items: To work through a section’s items in one dialog, one after another, select Review all.

Approve or deny a request

Lovable creates a request when a workspace policy requires approval before someone can publish, or before a project can enable Lovable backend services. Every admin and owner receives a notification in Lovable and by email. The table has four columns:
  • Request: who asked and for what, for example “Alex Chen wants to publish Sales dashboard”, with the requester’s note.
  • Blocking policy: the policy that requires approval for the request, such as Connectors, External collaborator, PII (personally identifiable information), External publishing, or Lovable backend services.
  • Expires in: how long until the request expires. Pending requests are sorted by expiry, soonest first, and a count shows how many expire today. For requests that were approved or denied, this column is Decided and shows the status and when it was approved or denied.
  • Actions: Approve and Deny. Approve approves the request from the row, without opening it. Deny opens the dialog where you give a reason.
Select a row to open the request before you approve or deny it. The dialog shows:
  • who asked, and their note,
  • a screenshot of the app, when Lovable has one,
  • the project, which opens in a new tab when you select its name,
  • for a publish request, how publishing changes who can see the app, for example from your workspace to the public,
  • the blocking policy, and
  • for the connectors policy, the connectors the app uses.
When you approve a request, Lovable carries out what the requester asked for:
  • A publish request: Lovable publishes the app. The approval then covers the requester’s later updates to the app until something the policy checks changes, or for the time set on the Restrict publishing externally policy. See How approvals work.
  • A request to enable Lovable backend services: Lovable sets the backend up for that project. The approval covers that project only.
Some requests Lovable cannot carry out for you. The dialog says so, and the requester finishes the work after your approval. To deny a request, choose a suggested reason, such as “Not ready to go public” or “Connectors need extra review”, or write your own, then select Deny request. The requester sees the reason, so write one they can act on. You cannot approve or deny a publish request you made, so another admin or owner does. When a request can only go to you, you approve or deny it yourself. Lovable notifies the requester of your decision. For a publish request, the requester follows it in the project’s publish dialog, described in Request approval to publish. For a backend services request, they follow it on the approval card in the project chat. Filter the table by requester, by policy, and by status:
  • Pending: waiting for a decision.
  • Approved and Denied: an admin or owner approved or denied the request.
  • Expired: nobody approved or denied the request in 30 days. A request that closed because the project changed while it waited shows here as Expired · project changed.
  • Cancelled: the requester withdrew the request, or sent a new request after updating the app.

Review findings that need attention

Needs attention lists findings from the workspace’s projects that need a decision. Each row shows a Review priority and an Identified date. The priority is High or Medium, and connector requests can also be Low. Lovable groups findings of the same kind and priority into one row, for example “4 projects used 620 credits in the last 7 days”. Filter by Missing owners, Security findings, Credit usage, Abandoned projects, or Connector requests, or search by project or owner. Reviewing a finding marks it as reviewed. It changes the project only when you choose an action that does so, such as transferring ownership, unpublishing, or ignoring security findings. For abandoned projects, marking the finding as reviewed also clears the abandoned label. For a project that is not shared with you, the finding shows that you have no access to it. You can mark the finding as reviewed, but you cannot unpublish or change the app. Ask the owner to share it.

Missing owners

Lovable flags every externally published (public) app whose owner is no longer an active member of the workspace. The row reads, for example, “3 externally published apps have no owner”, at Medium priority. Approval requests for these projects wait until the project has a new owner. Select Assign owners. For each project, choose a new owner under New owner. You can choose any active admin, owner, or editor. A project that only its owner could open can be transferred only to an admin or owner. Assign owner transfers the project and marks the finding as reviewed. The button is available only for projects you have permission to transfer. Mark all as reviewed clears the row without transferring anything, and the projects stay without an owner.

Security findings

Lovable flags externally published (public) apps that Security insights marks as critical. They appear here with High review priority. Apps below critical stay in Security insights and do not appear here. A row for a single app reads, for example, “Sales dashboard has open security findings”, with the number of critical findings and warnings. A row for several apps reads, for example, “4 projects have high review priority for security”. Supply chain findings, about packages with known security problems, are not counted here. Select Review findings on a single app’s row. Lovable lists each open finding with a Critical or Warning badge and a short description. On a row for several apps, select Review. Lovable lists each app with its owner and its number of critical findings and warnings. Select an app to see its findings. From an app’s findings, you can open the project’s Security view to fix them. To ignore every open finding in the project at once, select Ignore findings, then choose a reason or write your own. The row clears when the app is no longer critical, usually after you fix or ignore the findings. A later scan that finds critical issues flags the app again.
Ignore findings is the same action as ignoring a finding in the project’s Security view, applied to every open finding at once. The findings move to the ignored findings in the project’s Security view, stop counting toward its review priority, and critical findings stop blocking publishing.An ignored finding is not fixed. You can restore the findings from the project’s Security view.

Credit usage

Lovable flags a project whose run credits rose sharply. Run credits are the Cloud, AI gateway, and connector usage an app consumes while it runs, not the build credits you spend in the editor. Lovable flags a project when its daily usage over the last 7 days is at least 3 times its daily usage over the 28 days before. The 7 days must also add up to at least 50 credits. A project with no run usage in those 28 days is not flagged, however large the increase. Usage your plan’s included credits cover is counted too, so the number can be higher than the one in the project’s usage details. A 7-day total of 300 credits or more is High priority. Anything less is Medium. Select Review spend on a single project’s row to see the project’s usage. On a row for several projects, select Review to list each flagged project with the credits it used against its usual amount, then select a project. For each project, Lovable shows the last 7 days, the usual amount for 7 days, where the credits went, a chart of the last 28 days, and details about the project. Mark the finding as reviewed when the usage is expected, for example after a launch. The finding stays reviewed while the usage stays high, as described in How findings refresh.
On all paid plans, Lovable also sends workspace owners and admins an email and an in-app notification when the whole workspace’s run usage rises sharply. That alert compares one day against the previous 7, so it can arrive for a workspace with no flagged project here. See Why did Lovable alert me about higher-than-usual credit usage?

Abandoned projects

On Enterprise workspaces, Lovable flags externally published (public) apps that Lovable marked abandoned: nobody edited them for longer than the workspace’s abandonment period, 60 days by default. Anyone on the internet can open these apps, so Lovable asks you to decide whether they should stay live. The row reads, for example, “5 externally published projects are abandoned (no edits in over 60 days)”, at Medium priority. Select Review on the row to open a list of the apps. Each app shows its owner, its visits in the last 30 days, and its last edit, so you can tell an app people still use from one nobody opens. Select the projects, then choose either:
  • Keep published: Lovable clears the abandoned label and stops flagging the apps. Lovable flags them again only after the abandonment period passes again with no activity.
  • Unpublish: Lovable unpublishes the selected apps. An app that is not shared with you can only be marked as reviewed.
Each button shows the number of projects you selected. With nothing selected, you can mark all of them as reviewed instead.
Unpublish takes the published sites offline and their addresses stop working. Visitors with the old link cannot open the app until someone republishes it.

Connector requests

On Enterprise workspaces, Lovable lists the connectors that workspace editors asked for, as described in Connector requests. A row for one connector reads, for example, “3 users requested Slack in the last 30 days”. A row for several connectors reads, for example, “4 connectors were requested in the last 30 days”. The Review priority depends on how many editors asked for the connector: Low for one editor, Medium for 2 to 4, and High for 5 or more. On a single connector’s row, select Enable and set up for a disabled connector, or Set up for any other, to see who asked for the connector and the notes they added. On a row for several connectors, select Review, then select a connector. Lovable shows the 50 most recent requesters. You see a note only when you have access to the requester’s project. For each connector, choose one of these:
  • Enable and set up: for a connector that is disabled in your workspace. Lovable opens the connector’s settings in Connectors, where you enable it and create a connection.
  • Set up and the connector’s name, for example Set up Slack: for a connector that only workspace admins can connect. Lovable opens the connector’s settings in Connectors, where you create a connection and share it with the editors who asked.
  • Decline: closes the request. Add an optional reason of up to 500 characters. The editors who asked see the reason and can request the connector again.
Lovable notifies the editors who asked when the connector becomes available to them, for example after you create a connection they can use. Selecting Enable and set up or Set up does not notify them on its own. To decline every connector in a row for several connectors at once, select Review, then Decline all requests. Lovable notifies the editors who asked, without a reason.

How findings refresh

Lovable checks every Business and Enterprise workspace once a day, at 10:00 UTC. A new finding appears within a day of the problem starting. Findings about abandoned apps take up to 2 days, because Lovable applies the abandoned label after the daily check. A finding leaves the list as soon as you review it, and closes on its own when the problem ends. A fix you make closes the finding on the next daily check. A reviewed finding does not return while the same problem continues. When the problem ends and later starts again, Lovable opens a new finding that needs a new review. If some findings fail to load, the page says so. The findings that loaded are correct. Refresh the page to load the rest. On Enterprise workspaces, Lovable records reviews, ownership transfers, unpublished apps, and declined connector requests in the audit logs.