---
title: "Oladele David Temidayo (@oladele) | Hashnode"
description: "Gamer | Software Developer |Founder  | Love Football. Read the latest articles by Oladele David Temidayo on Hashnode."
url: "https://hashnode.com/@oladele"
---

@oladele

# Oladele David Temidayo

@oladele · Lagos, NG · Joined July 2020

Gamer | Software Developer |Founder | Love Football

[Website](https://oladeledavid.vercel.app/)

### [Onboarding Is a State Machine, Not a Boolean](https://oladele.hashnode.dev/onboarding-is-a-state-machine-not-a-boolean?utm_source=hashnode&utm_medium=feed)

A tenant is not "set up" or "not set up." It moves through ordered steps, can pause mid-flow, and must survive a refresh, a dropped payment, or a user who comes back three days later. This is how I model onboarding as a state the backend owns, and a guard that gates the rest of the product until that state says go.

14 min read · [oladele.hashnode.dev](https://oladele.hashnode.dev/onboarding-is-a-state-machine-not-a-boolean?utm_source=hashnode&utm_medium=feed)

[Jun 2](https://hashnode.com/posts/onboarding-is-a-state-machine-not-a-boolean/6a1eba1f60f0b6fd92e164b9)

### [Two Gates: Authorization vs Entitlement](https://oladele.hashnode.dev/two-gates-authorization-vs-entitlement?utm_source=hashnode&utm_medium=feed)

"Can this user do it?" and "does their plan allow it?" are two different questions. Most systems answer only the first, then bolt the second onto it badly. This is how I keep authorization and entitlement as two independent gates — and why mixing them is a mistake you pay for later.

14 min read · [oladele.hashnode.dev](https://oladele.hashnode.dev/two-gates-authorization-vs-entitlement?utm_source=hashnode&utm_medium=feed)

[Jun 2](https://hashnode.com/posts/two-gates-authorization-vs-entitlement/6a1eb5acc530a57b25deb6cc)

### [Turning a Permission Model Into a Guard](https://oladele.hashnode.dev/turning-a-permission-model-into-a-guard?utm_source=hashnode&utm_medium=feed)

A permission model that lives only in the database does nothing. This is the runtime layer, a declarative decorator and a guard that turns "who can do what" into an enforced answer on every request, without scattering authorization logic through your handlers.

12 min read · [oladele.hashnode.dev](https://oladele.hashnode.dev/turning-a-permission-model-into-a-guard?utm_source=hashnode&utm_medium=feed)

[Jun 2](https://hashnode.com/posts/turning-a-permission-model-into-a-guard/6a1eb292a9b38142247e62c3)

### [When "Admin" Means Two Different Things: Platform vs Organization Authority](https://oladele.hashnode.dev/when-admin-means-two-different-things-platform-vs-organization-authority?utm_source=hashnode&utm_medium=feed)

The word "admin" hides a fault line. On one side is authority over the whole platform. On the other is authority inside a single organization. This is how I keep those two planes from leaking into each other.

12 min read · [oladele.hashnode.dev](https://oladele.hashnode.dev/when-admin-means-two-different-things-platform-vs-organization-authority?utm_source=hashnode&utm_medium=feed)

[Jun 2](https://hashnode.com/posts/when-admin-means-two-different-things-platform-vs-organization-authority/6a1ea5069c95ffe337cee840)

### [How to Model Teams Inside a Multi-Tenant Product](https://oladele.hashnode.dev/how-to-model-teams-inside-a-multi-tenant-product?utm_source=hashnode&utm_medium=feed)

Once you have the tenant boundary, the next question is what lives inside it. This is how I modeled teams with roles, invitations, and lifecycle states that match real organizational behavior.

12 min read · [oladele.hashnode.dev](https://oladele.hashnode.dev/how-to-model-teams-inside-a-multi-tenant-product?utm_source=hashnode&utm_medium=feed)

[Jun 2](https://hashnode.com/posts/how-to-model-teams-inside-a-multi-tenant-product/6a1e412f81824da877dd0fde)
