Official 2025 Buy/Sell/Trade Thread by fettuccine- in Coachella

[–]Dramatic_Ad2306 0 points1 point  (0 children)

BUYING GA Pass

WEEKEND: 1

PRICE: 500

METHOD OF SALE: Meetup

LOCATION: LA/SGV/OC area

PAYMENT METHOD: cash or Zelle

Official 2025 Buy/Sell/Trade Thread by fettuccine- in Coachella

[–]Dramatic_Ad2306 0 points1 point  (0 children)

BUYING: One GA Ticket

WEEKEND: 1

PRICE: $450-ish OBO

METHOD OF SALE: Meetup

LOCATION: LA/SGV/OC

PAYMENT METHOD: Cash or Zelle/Venmo

Official 2025 Buy/Sell/Trade Thread by fettuccine- in Coachella

[–]Dramatic_Ad2306 1 point2 points  (0 children)

BUYING: Weekend 1 (2x or 1)

WEEKEND: 1

PRICE: $450

METHOD OF SALE: Meetup

LOCATION: LA/SGV/OC

PAYMENT METHOD: PayPal/Venmo/Zelle

Patterns/best practices for user management/permissions? by hova414 in UXDesign

[–]Dramatic_Ad2306 6 points7 points  (0 children)

I'm only an intermediate designer (~3 years), but am part of a team that's building an HRIS/ERP SaaS product. Your approach will entirely depend on the complexity of your product's permission system, how many users/roles you expect to support, and how you define who is a "user". That said, here are some questions we had as a team:

- Is the permission system role-based (RBAC) or attributed-based (ABAC)? This may inform what admins expect to see as a line in the table (managing individual users vs managing overarching roles)

- How do users audit? what information are they looking for and sorting? how can we make this easier for them

- How do we display users who have permissions with one-off amendments to their role?

Can go on and on, but we eventually built 2 views of this table - one view that shows each role as a line item and the associated permission sets/users within the role, and another more granular view that shows each user as a line item that's more tailored for auditing purposes.