shared inbox বনাম পৃথক account architectural decision। shared inbox বহু authorized person-কে এক address/history দেয়; separate account প্রতি identity-কে নিজ credential, recovery, activity ও lifecycle দেয়। কাজ shared queue না isolated identity—তার ওপর model নির্ভর।
guide legitimate support, project, test, research ও automation-এর জন্য। password sharing, misleading identity বা protection bypass নয়। required job দিয়ে শুরু ও simplest safe access model নিন।
দ্রুত তুলনা
| Factor | Shared inbox | Separate account |
|---|---|---|
| Purpose | many people one address manage | each identity task/test |
| History | member-centralized | account-প্রতি |
| Authentication | permission-based individual access | account-প্রতি login/recovery |
| Ownership | team/role | person/system |
| Examples | support@, billing@ | QA user, project identity |
| Risk | over-membership/unclear assignment | scattered credential/orphan account |
| Lifecycle | member/purpose review | account/owner/recovery/status review |
Team address-এ shared inbox
team member বদলালেও customer/vendor/employee ব্যবহৃত stable address-এ shared inbox fit। support, billing, recruiting, reception common। team shared history, stable sender ও password transfer ছাড়া admin-managed access list পায়।
- multiple authorized person same conversation পড়ে/reply।
- address person নয়, department।
- new member old context চাই।
- workflow assignment/status/shared calendar চাই।
- admin shared password ছাড়া member add/remove।
Google Groups-এ Collaborative Inbox ও password sharing ছাড়া Gmail delegation document করে। personal/managed account-এ feature বদলায়।
Microsoft Microsoft 365 shared mailbox-কে support/reception-এর multi-person inbox বলে। access permission-এ; mailbox account-এ direct sign-in intended নয়।
Independent identity-তে separate account
separate account আলাদা থাকা identity-তে fit। QA-তে signup, message, reset ও permission state না মেশাতে independent user লাগে। research/automation-এ অন্য system না ছুঁয়ে rotate/retire করা credential লাগতে পারে।
- প্রতি identity own login, inbox, recovery ও app।
- test distinct user emulate।
- project/client technical separation ও retention।
- এক compromise অন্য access না খুলে।
- shared public address না মুছে এক account retire।
এক app-এর multiple account পৃথক থাকে। Yahoo account switch document করে; identity ও login পৃথক। interface ownership, recovery বা state merge করে না।
এক password collaboration model নয়
password chat/record/sheet-এ copy করে standard inbox-কে shared করবেন না। provider delegation/membership নিন। separate identity-তে unique credential ও owner দিন।
Alias-কে দুই model-এর সঙ্গে গুলাবেন না
alias সাধারণত existing inbox-এর extra address। multiple name-এ mail নেয়, independent inbox/password/recovery/history নয়। many person-এ forward address-ও collaboration queue নাও হতে পারে।
need operational ভাষায় লিখুন: ‘পাঁচ agent one support history’, ‘দশ test user isolated reset’, বা ‘one owner second public address’। statement সঠিক model দেখায়।
দুই layer হলে hybrid
অনেক team দুটিই চায়। public address queue continuity-র জন্য shared; separate account পেছনের user/project/integration। shared inbox communication, account register identity isolation manage করে।
| Work layer | Model | Control |
|---|---|---|
| public support | shared inbox | member, permission, assignment owner |
| QA registration | separate account | environment, role, owner, expiry |
| department announcement | group/shared address | send/moderation permission |
| integration credential | separate if needed | system owner, vault ref, rotation |
| one person's alternate | alias | owner ও destination |
record link করুন, merge নয়। shared inbox record purpose/member/permission/review; separate register address/owner/recovery/status/vault ref। general register-এ secret নয়।
ছয় প্রশ্নের decision flow
- 1address owner person, team role, project না system?
- 2সবাই one history দেখবে, নাকি state isolated?
- 3প্রতি identity independent login/recovery/app/test behavior?
- 4shared secret-এর বদলে membership/delegation?
- 5কোন event access remove বা inbox retire?
- 6কোন admin setup verify ও next review record?
multiple operator-সহ stable address হলে shared/delegated model। independent-state identity হলে separate account ও provisioning workflow। দুটিই হলে hybrid boundary document।
Security, compliance ও review
individual authentication নিন, যাতে access attributable ও revocable। MFA, recovery, membership, delegation, session, forwarding ও app review। access review checklist keep/modify/suspend/retire process দেয়।
কোন model unsolicited message, impersonation বা control bypass অনুমতি দেয় না। usage/privacy/retention/communication rule মানুন। shared inbox-এ team sender; separate account-এ purpose/owner define।
MailCreator-এর fit
MailCreator separate Gmail, Yahoo বা Outlook account decision-এ fit; name, recovery, status ও CSV দেয়। Collaborative Inbox বা Microsoft 365 shared mailbox তৈরি/permission assign করে না।
authorized separate-account trial-এ Gmail, Yahoo বা Outlook। list, ownership, recovery ও retirement ready হলে মূল্য বা account তৈরি।