# CSS not available to Pro teams?

**URL:** <https://community.glideapps.com/t/css-not-available-to-pro-teams/56166>\
**Category:** Feature Requests\
**Created:** [December 30, 2022, 11:44am UTC](https://community.glideapps.com/t/css-not-available-to-pro-teams/56166 "2022-12-30T11:44:22Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Curtis](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/curtis/32/59826_2.png) [@Curtis](https://community.glideapps.com/u/Curtis)\
**Post date:** [December 30, 2022, 11:44am UTC](https://community.glideapps.com/t/css-not-available-to-pro-teams/56166/1 "2022-12-30T11:44:22Z")

</div>

The addition of CSS is great as it can be used to plug holes in functionality such as hiding certain components for specific screen/device sizes. This will make the pages much more user friendly on mobile.

It’s very odd that the CSS feature is not available to businesses on the Pro pricing tier? Are there any plans to expand it to Pro users?

---

<div class="post-metadata">

**Author:** ![Uzo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/uzo/32/22639_2.png) [@Uzo](https://community.glideapps.com/u/Uzo)\
**Post date:** [December 30, 2022, 12:36pm UTC](https://community.glideapps.com/t/css-not-available-to-pro-teams/56166/2 "2022-12-30T12:36:07Z")

</div>

… not … take Apps… but i heard… they will take it away too… but, don’t worry… i already have solutions for pages… i just don’t wanna mess with David too much…

---

<div class="post-metadata">

**Author:** ![Adam\_Xu](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/adam_xu/32/9762_2.png) [@Adam\_Xu](https://community.glideapps.com/u/Adam_Xu)\
**Post date:** [December 30, 2022, 4:41pm UTC](https://community.glideapps.com/t/css-not-available-to-pro-teams/56166/3 "2022-12-30T16:41:40Z")

</div>

I believe this would provide a huge incentive for Starter subscribers to get onboard with Pro. And it adds no burden to system, servers, etc.

---

<div class="post-metadata">

**Author:** ![Joe\_Gabriele](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/joe_gabriele/32/57595_2.png) [@Joe\_Gabriele](https://community.glideapps.com/u/Joe_Gabriele)\
**Post date:** [December 30, 2022, 5:03pm UTC](https://community.glideapps.com/t/css-not-available-to-pro-teams/56166/4 "2022-12-30T17:03:21Z")

</div>

I think their goal is to not appeal to B2C Apps, so if you want to use it for such, you’ll have to pay a lot. Also most B2C apps require a large amount of updates, which is provided in the Business Plan. CSS for the most part isnt a large focus for internal business apps as most users are forced to use the App their company created, whereas users on B2C can be turned off by poor UX or or on flip side, be attracted to use the app based on great design.

---

<div class="post-metadata">

**Author:** ![Adam\_Xu](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/adam_xu/32/9762_2.png) [@Adam\_Xu](https://community.glideapps.com/u/Adam_Xu)\
**Post date:** [December 30, 2022, 6:21pm UTC](https://community.glideapps.com/t/css-not-available-to-pro-teams/56166/5 "2022-12-30T18:21:47Z")

</div>

Thanks for the insight. I understand Glide’s position on B2C apps. Basically it is we warned you, but you are welcomed to try at your own risk 😀 But still, you can charge updates whichever way according to resource consumption, why not allow people the convenience if it costs nothing.

---

<div class="post-metadata">

**Author:** ![Curtis](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/curtis/32/59826_2.png) [@Curtis](https://community.glideapps.com/u/Curtis)\
**Post date:** [January 4, 2023, 11:11am UTC](https://community.glideapps.com/t/css-not-available-to-pro-teams/56166/6 "2023-01-04T11:11:34Z")

</div>

We’re using the pages for internal business apps. Good UX and UI is still required for internal use. This makes using them easier and less frustrating for staff, saving time and increasing productivity.  
Access to CSS for all “business” class pricing tiers would be the best thing.

---

<div class="post-metadata">

**Author:** ![David\_Gabler](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/david_gabler/32/44332_2.png) [@David\_Gabler](https://community.glideapps.com/u/David_Gabler)\
**Post date:** [January 4, 2023, 1:34pm UTC](https://community.glideapps.com/t/css-not-available-to-pro-teams/56166/7 "2023-01-04T13:34:38Z")

</div>

> [@Curtis](#):
>
> Access to CSS for all “business” class pricing tiers would be the best thing

Yes, and everyone seems to forget about B2B. If I want your business to use my SAAS app, it better be appealing. And making the app in Pro just makes sense in those cases.

---

<div class="post-metadata">

**Author:** ![Manikandan\_R](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/manikandan_r/32/43482_2.png) [@Manikandan\_R](https://community.glideapps.com/u/Manikandan_R)\
**Post date:** [January 4, 2023, 1:45pm UTC](https://community.glideapps.com/t/css-not-available-to-pro-teams/56166/8 "2023-01-04T13:45:54Z")

</div>

Hi David

Is still pages been used for small businesses?

I mean for marketplace?or a online shop

---

<div class="post-metadata">

**Author:** ![David\_Gabler](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/david_gabler/32/44332_2.png) [@David\_Gabler](https://community.glideapps.com/u/David_Gabler)\
**Post date:** [January 4, 2023, 1:56pm UTC](https://community.glideapps.com/t/css-not-available-to-pro-teams/56166/9 "2023-01-04T13:56:47Z")

</div>

> [@Manikandan\_R](#):
>
> Is still pages been used for small businesses?

Well, being developed for businesses, perhaps. So I need the features of Pro, but don’t need all the updates of Business Tier. Once a business adopts the app, they would, of course, be put on Business Tier.

---

<div class="post-metadata">

**Author:** ![David\_Gabler](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/david_gabler/32/44332_2.png) [@David\_Gabler](https://community.glideapps.com/u/David_Gabler)\
**Post date:** [January 4, 2023, 2:10pm UTC](https://community.glideapps.com/t/css-not-available-to-pro-teams/56166/10 "2023-01-04T14:10:48Z")

</div>

Check out this from @Gideon_Lahav_Busines. Could you see a “Pro” vs “Business” tier needing RTL?  
[RTL using CSS](https://community.glideapps.com/t/css-pages-rtl/56324)

---

<div class="post-metadata">

**Author:** ![Gideon\_Lahav\_Busines](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/gideon_lahav_busines/32/41121_2.png) [@Gideon\_Lahav\_Busines](https://community.glideapps.com/u/Gideon_Lahav_Busines)\
**Post date:** [January 4, 2023, 2:16pm UTC](https://community.glideapps.com/t/css-not-available-to-pro-teams/56166/11 "2023-01-04T14:16:21Z")

</div>

I wish this was for starter, this is a basic need for RTL future like this:

```auto
main {
  text-align: start;
  direction: rtl;
}

[class="mobile-tab-bar___StyledDiv2-sc-31qrn7-1 jzHsuz main-nav"] {
  text-align: start;
  direction: rtl;
}

[class="mobile-nav-bar___StyledDiv-sc-15t4b3x-2 isQoDT"]{
  text-align: start;
  direction: rtl;
}

.cBklgG {
  text-align: start;
  direction: rtl;
}

[class="sc-gsTCUz bvHOLJ card-collection-list___StyledGlideIcon-s6kvv4-14 jjKuvc arrow"] {
    transform: rotate(180deg);

}

[class="wire-button___StyledDiv-sc-1tlscdy-1 hDGVXA"] {
    transform: rotate(180deg);

}

```

---

<div class="post-metadata">

**Author:** ![David\_Gabler](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/david_gabler/32/44332_2.png) [@David\_Gabler](https://community.glideapps.com/u/David_Gabler)\
**Post date:** [January 4, 2023, 2:19pm UTC](https://community.glideapps.com/t/css-not-available-to-pro-teams/56166/12 "2023-01-04T14:19:37Z")

</div>

> [@Gideon\_Lahav\_Busines](#):
>
> I wish this was for starter,

Exactly!