Libraries tagged by Mail management

dalab/mail-management

0 Favers
4 Downloads

Mail management

Go to Download


frenchfrogs/mail

0 Favers
1024 Downloads

Mail Database management with frenchfrogs framework

Go to Download


netserva/mail

0 Favers
1 Downloads

NetServa Mail Infrastructure - Complete email server management with Postfix, Dovecot, and mailbox administration

Go to Download


anikninja/mail-mapper

1 Favers
15 Downloads

A Laravel package for dynamic, configurable email mapping and notification management.

Go to Download


au-vic-gov-dpc/user-management

1 Favers
579 Downloads

This module allows you to group users based on their available e-mail addresses and add multiple e-mail addresses to users

Go to Download


communityii/yii2-user-mailer-plugin

1 Favers
6 Downloads

A mail management module for Yii 2.0 with ability to manage mail queues, templates, and more.

Go to Download


finally-a-fast/fafcms-module-mailmanager

0 Favers
34 Downloads

This is an mail manager module for the Finally a fast CMS.

Go to Download


kapilpatel20/bvemailtemplate

0 Favers
36 Downloads

Email Template Management with eidt option

Go to Download


jrivera/filamentkit

1 Favers
14 Downloads

Kit de inicio para Filament con autenticación social y monitoreo de correos por J Rivera.

Go to Download


atm/mailbundle

0 Favers
306 Downloads

Mailing management bundle

Go to Download


snnyk/yandexmail

1 Favers
21 Downloads

Yandex corporate mail management library

Go to Download


maispace/mai-newsletter

0 Favers
0 Downloads

Newsletter management extension. **Owns the canonical subscriber record** — all opt-in/opt-out operations across the project write to this extension's subscriber table. Email dispatch goes through `mai_mail`.

Go to Download


retail-cosmos/ioi-city-mall-sales-file

2 Favers
36778 Downloads

The IOI City Mall Sales File Generator is a Laravel package that simplifies the creation of daily sales data files for IOI City Mall stores. It seamlessly integrates into Laravel projects, streamlining data generation for retail management.

Go to Download


adhocrat-io/arkhe-main

0 Favers
201 Downloads

Bootstrap a Laravel backend with users, roles and permissions management on Flux UI.

Go to Download


inda-hr/php_sdk

6 Favers
1354 Downloads

# Introduction **INDA (INtelligent Data Analysis)** is an [Intervieweb](https://www.intervieweb.it/hrm/) AI solution provided as a RESTful API. The INDA pricing model is *credits-based*, which means that a certain number of credits is associated to each API request. Hence, users have to purchase a certain amount of credits (established according to their needs) which will be reduced at each API call. INDA accepts and processes a user's request only if their credits quota is grater than - or, at least, equal to - the number of credits required by that request. To obtain further details on the pricing, please visit our [site](https://inda.ai) or contact us. INDA HR embraces a wide range of functionalities to manage the main elements of a recruitment process: + [**candidate**](https://api.inda.ai/hr/docs/v2/#tag/Resume-Management) (hereafter also referred to as **resume** or **applicant**), or rather a person looking for a job; + [**job advertisement**](https://api.inda.ai/hr/docs/v2/#tag/JobAd-Management) (hereafter also referred to as **job ad**), which is a document that collects all the main information and details about a job vacancy; + [**application**](https://api.inda.ai/hr/docs/v2/#tag/Application-Management), that binds candidates to job ads; it is generated whenever a candidate applies for a job. Each of them has a specific set of methods that grants users the ability to create, read, update and delete the relative documents, plus some special features based on AI approaches (such as *document parsing* or *semantic search*). They can be explored in their respective sections. Data about the listed document types can be enriched by connecting them to other INDA supported entities, such as [**companies**](https://api.inda.ai/hr/docs/v2/#tag/Company-Management) and [**universities**](https://api.inda.ai/hr/docs/v2/#tag/Universities), so that recruiters may get a better and more detailed idea on the candidates' experiences and acquired skills. All the functionalities mentioned above are meant to help recruiters during the talent acquisition process, by exploiting the power of AI systems. Among the advantages a recruiter has by using this kind of systems, tackling the bias problem is surely one of the most relevant. Bias in recruitment is a serious issue that affect both recruiters and candidates, since it may cause wrong hiring decisions. As we care a lot about this problem, we are constantly working on reduce the bias in original data so that INDA results may be as fair as possible. As of now, in order to tackle the bias issue, INDA automatically ignores specific fields (such as name, gender, age and nationality) during the initial processing of each candidate data. Furthermore, we decided to let users collect data of various types, including personal or sensitive details, but we do not allow their usage if it is different from statistical purposes; our aim is to discourage recruiters from focusing on candidates' personal information, and to put their attention on the candidate's skills and abilities. We want to help recruiters to prevent any kind of bias while searching for the most valuable candidates they really need. The following documentation is addressed both to developers, in order to provide all technical details for INDA integration, and to managers, to guide them in the exploration of the implementation possibilities. The host of the API is [https://api.inda.ai/hr/v2/](https://api.inda.ai/hr/v2/). We recommend to check the API version and build (displayed near the documentation title). You can contact us at [email protected] in case of problems, suggestions, or particular needs. The search panel on the left can be used to navigate through the documentation and provides an overview of the API structure. On the right, you can find (*i*) the url of the method, (*ii*) an example of request body (if present), and (*iii*) an example of response for each response code. Finally, in the central section of each API method, you can find (*i*) a general description of the purpose of the method, (*ii*) details on parameters and request body schema (if present), and (*iii*) details on response schema, error models, and error codes.

Go to Download


<< Previous Next >>