# Best way to present read-only data to end-users

**URL:** <https://community.glideapps.com/t/best-way-to-present-read-only-data-to-end-users/41362>\
**Category:** Ask for Help\
**Created:** [April 28, 2022, 3:35pm UTC](https://community.glideapps.com/t/best-way-to-present-read-only-data-to-end-users/41362 "2022-04-28T15:35:12Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![MattLB](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mattlb/32/41284_2.png) [@MattLB](https://community.glideapps.com/u/MattLB)\
**Post date:** [April 28, 2022, 3:35pm UTC](https://community.glideapps.com/t/best-way-to-present-read-only-data-to-end-users/41362/1 "2022-04-28T15:35:12Z")

</div>

I am using a detail screen from an in-line list and I do not want anyone to be able to edit the data unless they go to an edit screen.

Is there a way or a best practice on how to display data that is read-only. What I really want an option flag for the component so it can be viewed only and not changed!

For example, I have a boolean that shows up as a nice switch BUT the end-user can change this. I want it display only (as well as other fields).

Am I missing something?

TIA

---

<div class="post-metadata">

**Author:** ![MattLB](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mattlb/32/41284_2.png) [@MattLB](https://community.glideapps.com/u/MattLB)\
**Post date:** [April 28, 2022, 3:39pm UTC](https://community.glideapps.com/t/best-way-to-present-read-only-data-to-end-users/41362/2 "2022-04-28T15:39:59Z")

</div>

OK - LITERALLY the only component I didn’t try was ‘Table’ (which I am now testing) which gives me an ugly but read-only view of the data.

Any other options??

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [April 28, 2022, 3:41pm UTC](https://community.glideapps.com/t/best-way-to-present-read-only-data-to-end-users/41362/3 "2022-04-28T15:41:47Z")

</div>

You can build your own tables using a bit of Markdown or HTML in a template column, and then display it using a Rich Text component.

Here are a few examples:

> [@Basic Table Component](https://community.glideapps.com/t/basic-table-component/5804/58):
>
> I’d probably create an HTML table for this. It goes something like… create a template column that creates a \<tr\> row for each legend item, eg. \<tr\>\<td\>ICON\</td\>\<td\>NAME\</td\>\</tr\> create a Joined List column to string all those together - with no separator create a template column to insert that joined list inside some \<table\> tags, eg. \<table\>{joined-list}\</table\> then display that in a rich text component If you want to get fancy, you can use a [CSS table generator](https://divtable.com/table-styler/) and come up with some…

> [@zap Rich Text \> Actions!](https://community.glideapps.com/t/rich-text-actions/27273/12):
>
> Sure! One thing that isn’t obvious from the screen shot is that two of those tables are collapsable: That’s done in the usual way, using HTML \<details\>\<summary\> tags. Although getting it to play nicely with the tables was a bit fiddly. Anyway… I used [HTML Table Styler ▦ CSS Generator | 𝗗𝗜𝗩𝗧𝗔𝗕𝗟𝗘.𝗖𝗢𝗠](https://divtable.com/table-styler/) to come up with the basic table structure and CSS, and then butchered the CSS until I got it looking how I wanted. My CSS-fu is not very strong, so I suspect there is a lot of bloat the…

---

<div class="post-metadata">

**Author:** ![MattLB](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mattlb/32/41284_2.png) [@MattLB](https://community.glideapps.com/u/MattLB)\
**Post date:** [April 28, 2022, 3:58pm UTC](https://community.glideapps.com/t/best-way-to-present-read-only-data-to-end-users/41362/4 "2022-04-28T15:58:16Z")

</div>

I would prefer a read-only switch under options but this is a really good way and fits with the ‘Glide way’ of using rows as a means of storing display options like with templates. I use them for creating captions for card lists, etc.

Thanks for another tip!

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/system/32/53398_2.png) [@system](https://community.glideapps.com/u/system)\
**Post date:** [April 29, 2022, 3:58pm UTC](https://community.glideapps.com/t/best-way-to-present-read-only-data-to-end-users/41362/5 "2022-04-29T15:58:45Z")

</div>

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.