Emails
Emails | |
---|---|
Name: | Emails |
Tech Name: | Emails |
Class Name: | Emails |
Type: | Standard |
Template: | Security_groups, Assignable, Basic |
Custom Module: | No |
Auditable: | Yes |
Importable: | No |
Reportable: | Yes |
Hide module on Main Page: | No |
Contents
Short Description
The "Emails" module is designed to enhance and simplify email management within an organization. Its primary objective is to offer users a swift and efficient means to oversee their email correspondence while also serving as a comprehensive email repository. By presenting a concise presentation of email threads and pertinent message records, it empowers users to remain well-informed and current with their email communications.
Business Description
Overview
The 'Email' module is a important component of the system, designed to enhance communication and streamline correspondence management within an organization.Its primary purpose is to facilitate the creation, organization, and monitoring of email communications.
Within the 'Email' module, users can efficiently compose, send, receive, and organize emails. It serves as a centralized platform for managing both internal and external correspondence, fostering effective communication among team members and external contacts.
The 'Email' module incorporates a versatile feature known as the Activity subpanel, integrated into most other modules (e.g., Contacts, Customers, Tasks). This subpanel empowers users to create and send emails directly from within those modules, simplifying the communication process. It enables the seamless integration of email correspondence with other aspects of the organization, ensuring that communication is effectively intertwined with customer interactions, task management, and more. Furthermore, once an email is sent, it is automatically logged in the History subpanel, creating a comprehensive email history. This feature allows users to easily track and reference past email communications.
Fields
The Email module is comprised of multiple fields, each meticulously crafted with a distinct purpose in mind, serving to capture and organize essential email-related information. Here is a detailed explanation of each field:
Subject | The brief description or title of the email. | |
Body | The main content and message of the email. | |
Status | Status: The current state or status of the email (e.g., Draft, Sent, Received). | |
Date Created | The date and time when the email was initially created. | |
Date Modified | The date and time when the email was last edited or modified. | |
Related to | Related to: The entity or context to which the email is related (e.g., a Contact, Customer, or Task). | |
Category | The categorization or labeling of the email for easy reference. | |
From | The sender's email address or name. | |
To | The recipient's email address or name. | |
Cc | The carbon copy recipients of the email. | |
Bcc | The blind carbon copy recipients of the email. | |
Assigned User | The user responsible for managing or handling the email. |
Note: Fields marked with an asterisk are required. Saving the record without providing input to them beforehand won't be possible.
Relations
The Email module establishes relationships with several other modules within the system, allowing for seamless integration and efficient management of the recruitment process. These related modules include:
The 'Email' module plays a helpful role within the system by facilitating seamless communication and correspondence management. It forms essential connections with both the 'Candidates' and 'Project' modules.
In the context of the 'Candidates' module, the 'Email' module allows for the relation of email communications directly with candidate interactions. This means that recruiters and hiring teams can effortlessly send, receive, and archive emails related to specific candidates. It streamlines the recruitment process, ensuring that all communication with candidates is organized and easily accessible within the candidate's profile.
Similarly, the 'Email' module establishes crucial ties with the 'Project' module. It enables project teams to communicate effectively through emails related to project tasks, updates, and discussions. By centralizing email communication within the 'Project' module, teams can easily track project-related correspondence and maintain a comprehensive project history. This relation enhances collaboration, ensures that project-related emails are readily available to team members, and contributes to project management efficiency.
Role in the Hiring Process
The system's 'Email' module plays a central role in optimizing the Hiring Process. It acts as a communication hub, streamlining interactions between recruiters, hiring managers, and prospective candidates.
Within the hiring context, this module enables recruiters to efficiently manage email correspondence related to job postings, interview scheduling, and candidate evaluations. It ensures that information and updates are readily accessible, fostering better coordination among team members involved in the recruitment process.
The 'Email' module helps in preserving a comprehensive history of all hiring-related email exchanges, which can be invaluable for reference and compliance purposes. This feature enhances transparency and accountability in the hiring process.
Custom Actions
Processes
Related Processes
Related Process Steps
Process | Step Title | Short Description |
---|---|---|
Administration Guide | Email Settings | Manage outbound and inbound emails. The email settings must be configured in order to enable users to send out email and newsletter campaigns. |
Related Features
Affected by
Initiating
Related Integrations
Structure
Fields
Name | Type | Required | Validations | Visible | Editable |
---|---|---|---|---|---|
Assigned to | relate | No | Yes | Yes | |
Category | enum | No | Yes | Yes | |
Created By | relate | No | Yes | No | |
Date Created | datetime | No | Yes | No | |
Date Modified | datetime | No | Yes | No | |
Date Sent/Received | datetime | No | Yes | Yes | |
Email Status | enum | No | Yes | Yes | |
Email Template | relate | No | Yes | Yes | |
Flagged | bool | No | Yes | Yes | |
Has Attachments | function | No | Yes | Yes | |
IMAP Keywords | varchar | No | Yes | Yes | |
Indicator | function | No | Yes | Yes | |
Intent | varchar | No | Yes | Yes | |
Last Synchronised | datetime | No | Yes | Yes | |
Message ID | varchar | No | Yes | Yes | |
Modified By Name | relate | No | Yes | No | |
Opt In | function | No | Yes | Yes | |
Orphaned | bool | No | Yes | Yes | |
Parent Type | varchar | No | Yes | Yes | |
Related To | parent | No | Yes | Yes | |
Reply To Status | bool | No | Yes | Yes | |
Subject | function | No | Yes | Yes | |
Subject | name | No | Yes | Yes | |
Type | enum | No | Yes | Yes | |
bcc_addrs_names | varchar | No | Yes | Yes | |
cc_addrs_names | varchar | No | Yes | Yes | |
description | text | No | Yes | Yes | |
description_html | emailbody | No | Yes | Yes | |
raw_source | varchar | No | Yes | Yes | |
reply_to_addr | varchar | No | Yes | Yes | |
to_addrs_names | varchar | No | Yes | Yes |
Relationships
Laft | Type | Right | Short Description | Relationship |
---|---|---|---|---|
Candidates | many-to-many | Emails | Many Candidate records can be related to many Email records | Relationship: Candidates - Emails |
Emails | one-to-many | Meetings | One Email record can have many related Meeting records, but a specific Meeting record can be related to only one Email record. | Relationship: Emails - Meetings |
Emails | one-to-many | Notes | One Email record can have many related Note records, but a specific Note record can be related to only one Email record. | Relationship: Emails - Notes |
Project | one-to-many | Emails | Flex relate used in Project | Relationship: Project - Emails |
Project Tasks | one-to-many | Emails | Flex relate used in Project Task | Relationship: ProjectTask - Emails |
Users | one-to-many | Emails | Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user. | Relationship: Users - Emails |
Users | one-to-many | Emails | Specific Sugar user can create many account records, but specific account record can be created by only one user. | Relationship: Users - Emails |
Users | one-to-many | Emails | Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned. | Relationship: Users - Emails |