# Why are bucket names not encrypted?

**URL:** <https://forum.storj.io/t/why-are-bucket-names-not-encrypted/15382>\
**Category:** Product Discussions\
**Created:** [September 21, 2021, 5:52am UTC](https://forum.storj.io/t/why-are-bucket-names-not-encrypted/15382 "2021-09-21T05:52:04Z")\
**Posts on this page:** 2\
**Page:** 2

<div class="post-metadata">

**Author:** ![Knowledge](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/knowledge/32/10681_2.png) [@Knowledge](https://forum.storj.io/u/Knowledge)\
**Post date:** [November 17, 2021, 4:47pm UTC](https://forum.storj.io/t/why-are-bucket-names-not-encrypted/15382/21 "2021-11-17T16:47:11Z")

</div>

I think Jammerdan’s concern is valid here. You create a bucket, the default grant is to apply everyone access to all your buckets. This is easy to just hit OK and miss that instead of giving Everyone access to that one bucket, you just opened up everything by mistake.

I agree, that people should pay attention. But it would make more sense, in my opinion, that if you create a bucket, that the grant menu defaults to showing just that new bucket as selected. And not All Buckets. It would reduce the potential for error.

---

<div class="post-metadata">

**Author:** ![bre](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/bre/32/69_2.png) [@bre](https://forum.storj.io/u/bre)\
**Post date:** [November 17, 2021, 4:57pm UTC](https://forum.storj.io/t/why-are-bucket-names-not-encrypted/15382/22 "2021-11-17T16:57:09Z")

</div>

+1 on preemptively preventing errors

[Previous page](https://forum.storj.io/t/why-are-bucket-names-not-encrypted/15382.md?page=1)
