# Account States Example

Alice works for MeetingSpace (a teleconferencing service provider) as the Account Administrator for OmniDesk (one of MeetingSpace's client companies). OmniDesk's new employee John Catherwood calls MeetingSpace to set up an account.

When Alice first creates the account, the system automatically places it in Pending Active Approval (MeetingSpace uses Active Pending Approval in their MetraNet configuration). Alice sets up the account's subscriptions.

Sam, Alice's supervisor, logs into Account Manager and examines John's account to see if all the subscriptions are correct, John's account is in the right folder, and so on. Everything checks out. So he places John's account in an Active state.

A few months later, John Catherwood calls Alice and tells her he is going on vacation for three weeks. Alice changes John's account to Suspended, effective on the date he is leaving, and moving back to Active three weeks later.

Two weeks later, John calls Alice to inform her that he's back from vacation early. Alice changes John's account state to Active, effective on the date he came back.

Much later, John Catherwood calls Alice again. He announces that he's leaving Omnidesk in two weeks. Alice places John's account in a Closed state, effective in two weeks. John's invoice isn't scheduled to be generated for another three weeks. Therefore, in two weeks the account will be in a Pending Final Bill state. A week after that, MetraNet will generate John Catherwood's final invoice and his account will be in a Closed state.

OmniDesk has configured MetraNet to place accounts in an Archived state for two months after they move to Closed. Therefore, John Catherwood's account will appear in OmniDesk's hierarchy for two months as Closed. After that, John's account will only be visible when viewing OmniDesk's hierarchy using past dates.