# Feature Request - Field-Level Authentication (e.g., PIN or Memorable Word Prompt for Sensitive Fields)

**URL:** <https://community.noloco.io/t/feature-request-field-level-authentication-e-g-pin-or-memorable-word-prompt-for-sensitive-fields/2248>\
**Category:** Feature Requests\
**Tags:** feature-request\
**Created:** [October 30, 2025, 8:25pm UTC](https://community.noloco.io/t/feature-request-field-level-authentication-e-g-pin-or-memorable-word-prompt-for-sensitive-fields/2248 "2025-10-30T20:25:01Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![simoneastwood](https://avatars.discourse-cdn.com/v4/letter/s/6bbea6/32.png) [@simoneastwood](https://community.noloco.io/u/simoneastwood)\
**Post date:** [October 30, 2025, 8:25pm UTC](https://community.noloco.io/t/feature-request-field-level-authentication-e-g-pin-or-memorable-word-prompt-for-sensitive-fields/2248/1 "2025-10-30T20:25:01Z")

</div>

Field-Level Authentication (e.g., PIN or Memorable Word Prompt for Sensitive Fields)

**Description:**  
I’d like to request a feature that allows true field-level authentication in Noloco. Specifically, I want the ability to require users to enter a PIN, password, or selected characters from a memorable word before they can view or edit certain sensitive fields in a record—even after they’re logged in.

**Use Case:**

- When opening a customer record, before showing contact information or sensitive details, prompt the user to enter 2 characters from the customer’s memorable word (or a PIN/password).

- This would help us comply with security best practices and industry regulations for handling customer data.

- It would also allow us to add an extra layer of protection for highly sensitive information, even for authenticated users.

**Why it matters:**

- Role-based permissions are great, but sometimes we need an extra layer of security for specific fields.

- Field-level authentication is common in financial, healthcare, and security-focused apps.

- This would make Noloco even more suitable for sensitive business use cases.

---

<div class="post-metadata">

**Author:** ![darragh](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/darragh/32/12_2.png) [@darragh](https://community.noloco.io/u/darragh)\
**Post date:** [November 3, 2025, 7:49am UTC](https://community.noloco.io/t/feature-request-field-level-authentication-e-g-pin-or-memorable-word-prompt-for-sensitive-fields/2248/2 "2025-11-03T07:49:43Z")

</div>

Hey @simoneastwood - we wouldn’t usually reccomend storing such data in Noloco, for a lot of the reasons you’ve mentioned.

Is this for building a SaaS application?

We don’t typically see this need in the Business app space, which is why it’s not much of a priority for us.

---

<div class="post-metadata">

**Author:** ![simoneastwood](https://avatars.discourse-cdn.com/v4/letter/s/6bbea6/32.png) [@simoneastwood](https://community.noloco.io/u/simoneastwood)\
**Post date:** [November 6, 2025, 9:20pm UTC](https://community.noloco.io/t/feature-request-field-level-authentication-e-g-pin-or-memorable-word-prompt-for-sensitive-fields/2248/3 "2025-11-06T21:20:49Z")

</div>

I have made a crm app for my business, this feature would help alot with the functionality I require.

---

<div class="post-metadata">

**Author:** ![simoneastwood](https://avatars.discourse-cdn.com/v4/letter/s/6bbea6/32.png) [@simoneastwood](https://community.noloco.io/u/simoneastwood)\
**Post date:** [November 6, 2025, 9:22pm UTC](https://community.noloco.io/t/feature-request-field-level-authentication-e-g-pin-or-memorable-word-prompt-for-sensitive-fields/2248/4 "2025-11-06T21:22:01Z")

</div>

This feature would help to secure specific information as outlined in my request