Dismiss RLS recommendation

This API is in beta. Endpoints, fields, and behavior may still change, so avoid depending on it in production.

Removes one entity’s row-level security recommendation from the app’s latest security scan result. Get entity_name from rls_recommendations in Get security scan.

The call changes only the scan result, never the entity’s rules. You can send it two ways:

• Send applied_rule to record a fix. Apply the rules with Update entity schema first, because Base44 records the rules as you send them and doesn’t check them against the entity.
• Leave applied_rule out to dismiss the recommendation without recording a fix.

The next scan that checks row-level security judges every entity again, so a recommendation can come back if the entity’s rules still need to change.

DELETE /api/apps/{app_id}/security/scan/rls-recommendation/{entity_name}

Dismiss RLS recommendation

cURL

curl --request DELETE \
  --url https://app.base44.com/api/apps/{app_id}/security/scan/rls-recommendation/{entity_name} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "applied_rule": {
    "create": true,
    "read": {
      "created_by": "{{user.email}}"
    },
    "update": {
      "created_by": "{{user.email}}"
    },
    "delete": {
      "$or": [
        {
          "created_by": "{{user.email}}"
        },
        {
          "user_condition": {
            "role": "admin"
          }
        }
      ]
    }
  }
}
'

200

{
  "status": "ok"
}

Authorizations

Authorization · string · header · required

Personal access token, sent as Authorization: Bearer <token>. Each operation lists the permission it needs: read_only or full_access. A full-access token can call every operation. A read-only token can call only the operations that list read_only; anything else returns 403 read_only_credential_route_not_allowed.

Path Parameters

entity_name · string · required

Entity whose recommendation to remove, as returned in rls_recommendations by Get security scan. It contains only letters, digits, and underscores.

app_id · string · required

ID of the app.

Body

application/json

applied_rule · object | null

The rules you applied to the entity, keyed by operation in the same format as the entity's rls. Send it to record the call as a fix. Leave it out, or send null or an empty object, to record a plain dismissal. Keys other than the five operations are rejected.

A filter can use only the query operators $eq, $ne, $gt, $gte, $lt, $lte, $in, $nin, $and, $or, $not, $nor, $exists, $type, $all, $elemMatch, $size, $regex, $options, $text, $search, $near, $nearSphere, $geoIntersects, and $geoWithin. The operators $and, $or, and $nor take a list. The operators $in, $nin, and $all take a list or a template string such as {{user.data.departments}}. The user_condition key takes an object.

The whole value can be up to 20,000 bytes as compact JSON, nest up to 8 levels deep, and hold up to 200 keys in total. Lists can hold up to 50 items, keys up to 200 characters, and strings up to 2,000 characters. The keys __proto__, constructor, and prototype aren't allowed.

Show child attributes

Example:

{
  "create": true,
  "read": { "created_by": "{{user.email}}" },
  "update": { "created_by": "{{user.email}}" },
  "delete": {
    "$or": [
      { "created_by": "{{user.email}}" },
      { "user_condition": { "role": "admin" } }
    ]
  }
}

Response

200

application/json

The recommendation left the scan result.

status · string · required

Always ok. The recommendation is no longer in the scan result.

Example:

"ok"